Contribution records
Draft
Contributors

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

Give credit to everyone
greatmatter greatmatter
valthebald valthebald
fazni fazni volunteering
mikkmiggur mikkmiggur
sutharsan sutharsan organization(s): ronder
mohrerao mohrerao volunteering organization(s): Material customer(s): Drupal India Association
darrindeal darrindeal volunteering
tanubansal tanubansal organization(s): Salsa Digital
mayurjadhav mayurjadhav organization(s): Material
lauriii lauriii organization(s): Acquia
larowlan larowlan organization(s): PreviousNext
alucinogenado tiago.simoes
gauravvvv Gauravmahlawat organization(s): Axelerant customer(s): Drupal India Association
simon peacock simon-peacock
.tom tom_git customer(s): European Commission and European Union Institutions, Agencies and Bodies
abhijith s AbhijithS volunteering organization(s): Zyxware Technologies
sahil.goyal sahil.goyal volunteering organization(s): Material customer(s): Drupal India Association
rodrigoaguilera rodrigoaguilera volunteering
sanket.tale stale
mradcliffe mradcliffe volunteering organization(s): Kosada
mayurgajar mayurgajar
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.