Contribution records
Contributors

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

Give credit to everyone
saschaeggi saschaeggi volunteering
huzooka huzooka organization(s): Cheppers customer(s): Acquia
ckrina ckrina organization(s): Lullabot
lauriii lauriii organization(s): Acquia
kostyashupenko kostyashupenko organization(s): Skilld
komalk kkolekar organization(s): Material customer(s): Drupal India Association
dyannenova Nova organization(s): Acquia
tanubansal tanubansal organization(s): Salsa Digital
jwilson3 jwilson3 organization(s): Bluespark
rkoller rkoller
deviantintegral deviantintegral organization(s): Lullabot
alexpott alexpott organization(s): Acro Commerce, Thunder
aaronmchale AaronMcHale
benjifisher benjifisher volunteering organization(s): FRUITION
mherchel mherchel
cindytwilliams cindytwilliams organization(s): Kanopi Studios
xjm xjm organization(s): Acquia
rootwork rootwork volunteering
nod_ nod_ organization(s): Acquia
raman.b ramanbatra1709 organization(s): OpenSense Labs
abhijith s AbhijithS volunteering organization(s): Zyxware Technologies
gábor hojtsy goba organization(s): Acquia
andy-blum ablum organization(s): Lullabot
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.