Issue
Contribution records
Contributors

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

Give credit to everyone
jenlampton
eclipsegc
c4rl
sun
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
Crell volunteering organization(s): Palantir.net
joelpittet volunteering
jibran volunteering
markhalliwell organization(s): Tag1 Consulting, Inc.
almaudoh
yogeshmpawar organization(s): QED42
MerryHamster organization(s): Skilld customer(s): Skilld
vacho organization(s): Skilld
andypost volunteering organization(s): Skilld
star-szr
podarok
nicxvan organization(s): nLightened Development LLC
berdir organization(s): MD Systems GmbH
longwave organization(s): Full Fat Things
dcam
alexpott organization(s): Acro Commerce, Thunder
larowlan organization(s): PreviousNext
gábor hojtsy organization(s): Acquia
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.