Contribution records
Contributors

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

Give credit to everyone
rbaprado rbaprado volunteering
cilefen cilefen volunteering
dawehner dereine volunteering
jackalope jackalope
dbt102 dbt102 organization(s): Pineshore customer(s): Smoky Mountain Institute
pameeela pameeela organization(s): Technocrat
samiullah samiullah organization(s): Salsa Digital
quietone quietone volunteering organization(s): PreviousNext
borisson_ borisson_ organization(s): Calibrate
yashingole yashingole organization(s): QED42 customer(s): Drupal India Association
lucassc lucassc organization(s): CI&T
longwave longwave organization(s): Full Fat Things
catch catch organization(s): Third and Grove
bisw bisw
sourabh.singhal sourdrup organization(s): Faichi Solutions Pvt Ltd customer(s): Faichi Solutions Pvt Ltd
amol.palhade17 amol.palhade17 volunteering organization(s): Trigyn Technologies Ltd
priyanka.sahni priyanka.sahni organization(s): Material customer(s): Drupal India Association
norman.lol koiwo volunteering organization(s): 1xINTERNET
abhijith s AbhijithS 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.