Contribution records
Contributors

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

Give credit to everyone
ckrina ckrina organization(s): Lullabot
saschaeggi saschaeggi organization(s): Unic
sd9121 sd9121 volunteering
jwilson3 jwilson3 organization(s): Bluespark
bnjmnm bnjmnm organization(s): Acquia
meenakshig MeenakshiGupta organization(s): OpenSense Labs customer(s): Drupal India Association
hansa11 hansa11 volunteering organization(s): Ramsalt Lab
mgifford mgifford
chetanbharambe chetan18 customer(s): Drupal India Association
bradleyfmash bradmash volunteering organization(s): Kanopi Studios
paulocs paulocs organization(s): CI&T
marcusvsouza marcusvsouza organization(s): CI&T
lauriii lauriii organization(s): Acquia
kiran.kadam911 kiran.kadam911 organization(s): QED42 customer(s): Drupal India Association
javi-er javier organization(s): Lullabot
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.