Contribution records
Draft
Contributors

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

Give credit to everyone
chx chx
dawehner dereine
vj Vj
rpayanm rpayanm organization(s): SeeD EM
acrosman acrosman organization(s): Message Agency
willzyx willzyx
msgph msgph volunteering organization(s): Mearra (formerly known as Wunder)
duaelfr DuaelFr volunteering organization(s): Happyculture
mitrpaka mitrpaka organization(s): Mearra (formerly known as Wunder)
pwolanin pwolanin volunteering organization(s): Acquia
ajits ajits volunteering organization(s): QED42
vacho vacho organization(s): Skilld
hardik_patel_12 Hardik_Patel_12 organization(s): QED42 customer(s): Drupal India Association
rajandro Rajandro volunteering organization(s): Material customer(s): Drupal India Association
longwave longwave organization(s): Full Fat Things
davidmv97 DavidMV97 organization(s): SeeD EM customer(s): SeeD EM
sarathkm sarath49 volunteering
xjm xjm organization(s): HeroDevs
Yogesh Sahu YogeshSahu0 organization(s): OpenSense Labs customer(s): DrupalFit
binoli lalani binoli-lalani organization(s): QED42 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.