Contribution records
Contributors

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

Give credit to everyone
idebr idebr organization(s): iO
catch catch organization(s): Third and Grove
gauravvvv Gauravmahlawat organization(s): OpenSense Labs
drase15 drase15
seanb seanB
fengtan Fengtan volunteering organization(s): McGill University
ambikahirode ambikahirode volunteering organization(s): Material customer(s): Drupal India Association
vikashsoni vikashsoni volunteering
bnjmnm bnjmnm organization(s): Acquia
xjm xjm organization(s): Agileana
gabesullice gabesullice organization(s): Applura customer(s): IFundWomen
dqd dqd volunteering organization(s): MAROQQO studios
lauriii lauriii organization(s): Acquia
el7cosmos el7cosmos organization(s): PreviousNext
smustgrave smustgrave organization(s): Mobomo
tivi22 tivi22
joseph.olstad joseph.olstad
abhijith s AbhijithS volunteering organization(s): Zyxware Technologies
omkar.podey omkar.podey 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.