Contribution records
Contributors

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

Give credit to everyone
heather heather
wylbur wylbur volunteering
runeasgar runeasgar volunteering
benjifisher benjifisher organization(s): Isovera customer(s): Pegasystems
ifrik ifrik
catch catch organization(s): Third and Grove
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
chetanbharambe chetan18 organization(s): QED42 customer(s): Drupal India Association
quietone quietone volunteering
rootwork rootwork
bebalachandra bebalachandra volunteering organization(s): Material customer(s): Drupal India Association
nod_ nod_ volunteering organization(s): Acquia
aaronmchale AaronMcHale
rkoller rkoller
simohell simohell organization(s): Druid
Tor Arne Thune torthu
gábor hojtsy goba organization(s): Acquia
eli-on-drupal eli-on-drupal organization(s): Mindgrub Technologies
sahil rohilla01 SAHIL_ROHILLA organization(s): OpenSense Labs
Manoj Raj.R immanojraj volunteering organization(s): ITT Digital
gaurav-mathur gaurav-mathur organization(s): Dotsquares Ltd.
sahil.goyal sahil.goyal volunteering organization(s): Material customer(s): Drupal India Association
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.