Contribution records
Contributors

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

Give credit to everyone
mikeker mikeker volunteering
dawehner dereine
alexpott alexpott
jeanfei jeanfei
joelpittet joelpittet
sasanikolic sasanikolic volunteering
rajeshwari10 rajeshwari10 volunteering organization(s): Blisstering Solutions
lluvigne lluvigne organization(s): 1xINTERNET
gnuget gnuget volunteering organization(s): Agaric
shadcn arshad
xjm xjm organization(s): Zoocha, xjm, QED42
sidharthap sidharthap
rassoni soni.rashu organization(s): Material customer(s): Drupal India Association
smustgrave smustgrave organization(s): Mobomo
ankit_rathore ankit_rathore organization(s): OpenSense Labs customer(s): DrupalFit
wim leers wimleers volunteering organization(s): Acquia
mdranove mdranove
gengo_k gengo_k
ressa ressa
quietone quietone organization(s): PreviousNext
bramdriesen bramdriesen volunteering organization(s): Sopra Steria
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.