Issue
Contribution records
Contributors

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

Give credit to everyone
finnsky organization(s): Skilld
m4olivei organization(s): Lullabot
plopesc organization(s): Lullabot
nod_ organization(s): Très Bien Tech
gauravvvv organization(s): Axelerant customer(s): Drupal India Association
smustgrave organization(s): Mobomo
quietone organization(s): PreviousNext
ckrina organization(s): Lullabot
catch organization(s): Third and Grove
katannshaw organization(s): Lullabot
vladimiraus organization(s): Tomato Elephant Studio
gxleano organization(s): Factorial.io
rkoller
pameeela organization(s): Technocrat
mherchel organization(s): Dripyard
larowlan organization(s): PreviousNext
kentr volunteering
grimreaper organization(s): Smile
joelpittet organization(s): The University of British Columbia
oily volunteering
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.