Issue
Contribution records
Contributors

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

Give credit to everyone
berdir organization(s): MD Systems GmbH
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
catch organization(s): Third and Grove
andypost volunteering organization(s): Skilld
adamps organization(s): AlbanyWeb
matthiasm11 organization(s): Randstad Digital
bkosborne volunteering organization(s): Princeton University
darvanen
larowlan organization(s): PreviousNext
alexpott organization(s): Acro Commerce, Thunder
effulgentsia organization(s): Acquia
roy_k
geek-merlin organization(s): Geeks4Change, MachbarMacher
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.