Issue
Contribution records
Contributors

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

Give credit to everyone
swentel
joachim
joates
Stalski
yoroy
acabouet
jsobiecki
rwojenka
rpayanm
dahousecat
Bojhan volunteering
thomasdegraaff
amanire
cluther
chris_h
aburke626
xjm organization(s): Acquia
David_Rothstein volunteering
novitsh volunteering organization(s): Colruyt Group Services
HeimdallJHM organization(s): ASPgems
sdstyles organization(s): JAKALA (formerly FFW)
dani3lr0se volunteering
klonos organization(s): Backdrop CMS
ivan zugec
vineet.osscube
joshi.rohit100
Reno Greenleaf
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.