Contribution records
Contributors

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

Give credit to everyone
neochief neochief
jim0203 jim0203
dcor dcor
gpk gpk
skirpichev skirpichev
drupal_was_my_past rocket
David_Rothstein drothstein
andypost andypost volunteering organization(s): Skilld
krishworks krishworks
talhaparacha talhaparacha volunteering
surbz surbz organization(s): Material
shaktik shaktik volunteering organization(s): Material customer(s): Drupal India Association
samiullah samiullah organization(s): Salsa Digital
mayurjadhav mayurjadhav organization(s): Material
dries dries
larowlan larowlan
quietone quietone volunteering
adityasingh adityasingh volunteering organization(s): Material customer(s): Drupal India Association
anmolgoyal74 anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
guilhermevp guilhermevp organization(s): CI&T
pameeela pameeela
bnjmnm bnjmnm organization(s): Acquia
dave reid davereid
Tor Arne Thune torthu
abhijith s AbhijithS volunteering organization(s): Zyxware Technologies
Madhu kumar Madhu_kumar volunteering organization(s): Zyxware Technologies
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.