Issue
Contribution records
Contributors

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

Give credit to everyone
idebr organization(s): iO
berdir organization(s): MD Systems GmbH
fabianx volunteering
davidwhthomas
andypost volunteering organization(s): Skilld
akalam organization(s): Metadrop
johnchque organization(s): MD Systems GmbH
jibran volunteering
neclimdul organization(s): APQC
amateescu customer(s): Pfizer, Inc.
longwave organization(s): Full Fat Things
acbramley organization(s): PreviousNext customer(s): Service NSW
kualee
pameeela
larowlan organization(s): PreviousNext
xjm organization(s): Acquia
alexpott organization(s): Acro Commerce, Thunder
phenaproxima organization(s): Acquia
catch organization(s): Third and Grove
pratikshad volunteering
wim leers organization(s): Acquia
kim.pepper organization(s): PreviousNext
arpad.rozsa organization(s): Studio Present
joseph.olstad
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.