Issue
Contribution records
Draft
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
smustgrave organization(s): Mobomo
larowlan organization(s): PreviousNext
feyp volunteering organization(s): werk21
andypost volunteering organization(s): Skilld
ressa organization(s): Ardea
berdir organization(s): MD Systems GmbH
sime organization(s): ICON
dgsiegel
plopesc organization(s): Lullabot customer(s): IndieCommerce - Website Development for Independent Booksellers
sokru volunteering
mstrelan organization(s): PreviousNext
dqd volunteering organization(s): MAROQQO studios
samuhe volunteering
longwave organization(s): Full Fat Things
w01f volunteering organization(s): Timbers Dev
scotwith1t organization(s): Riva Solutions Inc customer(s): US Department of Agriculture
kopeboy
mattdanger organization(s): Forum One
catch organization(s): Third and Grove
quietone organization(s): PreviousNext
idiaz.roncero customer(s): La Cañamería Global S.L.
eduardo morales alberti volunteering organization(s): Metadrop
poker10 organization(s): ActivIT s.r.o.
idebr organization(s): iO
claudiu.cristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
Git commit message
Commit types
  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.