Contribution records
Contributors

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

Give credit to everyone
jonathanshaw jonathanjfshaw
adamps AdamPS organization(s): AlbanyWeb
eelkeblok eelkeblok organization(s): One Shoe
rootwork rootwork
samvel asik organization(s): DrupalJedi
berdir berdir organization(s): MD Systems GmbH
lauriii lauriii volunteering
adrian83 adrian83
alexpott alexpott
andypost andypost volunteering organization(s): Skilld
kingdutch Kingdutch organization(s): Open Social
jofitz jofitz organization(s): ComputerMinds, jofitz
oriol_e9g oriole9g organization(s): Diputació de Barcelona
larowlan larowlan organization(s): PreviousNext
thejimbirch thejimbirch organization(s): Kanopi Studios
dqd dqd volunteering organization(s): MAROQQO studios
plach plach volunteering
pancho pancho volunteering
imclean imclean
skaught SKAUGHT volunteering
xjm xjm 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.