Contribution records
Draft
Contributors

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

Give credit to everyone
shaal shaal volunteering organization(s): Palantir.net
jasonawant jwant organization(s): Nerdery
pawandubey pawandubey619 volunteering organization(s): TATA Consultancy Services
chandrashekhar_srijan chandrashekhar_srijan organization(s): Material customer(s): Drupal India Association
luco luco organization(s): Hogarth Worldwide
meenakshi_j Meenakshi organization(s): Material customer(s): Drupal India Association
adsyy adsyy volunteering
mellowtothemax mellowtothemax
nicrodgers nicrodgers organization(s): Welsh Government
jonnyhocks jonnyhocks organization(s): Welsh Government
abhijith s AbhijithS volunteering organization(s): Zyxware Technologies
gaurav-mathur gaurav-mathur organization(s): Dotsquares Ltd.
sonam.chaturvedi sonam.chaturvedi organization(s): Salsa Digital
quietone quietone organization(s): PreviousNext
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.