Issue
Contribution records
Contributors

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

Give credit to everyone
PatrickHaemelinck
CG_TSV volunteering
Irbis
cilefen
neclimdul organization(s): APQC
drupalsilm
davidhk
czunigaco organization(s): Kanopi Studios
yookoala organization(s): Pixel Action Studio
almador
ladybug_3777
poker10 organization(s): ActivIT s.r.o.
benjifisher volunteering organization(s): Tag1 Consulting, Inc.
rhip organization(s): Reading Room
klausi organization(s): jobiqo - job board technology
mcdruid organization(s): Acquia
dd 85
stefanos.petrakis volunteering
joseph.olstad
adinan cenci
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.