Issue
Contribution records
Contributors

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

Give credit to everyone
JayBeeDutch volunteering
aralnoth
cilefen volunteering
carsteng organization(s): JAKALA (formerly FFW)
eyilmaz organization(s): JAKALA (formerly FFW)
alexpott organization(s): Acro Commerce, Chapter Three (acquired by Kanopi Studios), Thunder
flocondetoile organization(s): Flocon de toile
Thew organization(s): Google Code-In
denutkarsh organization(s): Google Code-In
lomasr organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
marcvangend volunteering organization(s): Triquanta
mikeohara
bsnodgrass
idebr organization(s): ezCompany
szeidler organization(s): Ramsalt Lab
ckaotik organization(s): werk21
hhigel volunteering
gagarine volunteering
chegor organization(s): OAO Solution Spark
xjm organization(s): Acquia
catch organization(s): Third and Grove
amit.drupal volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
claudiu.cristea volunteering organization(s): Webikon
didier misson volunteering
geek-merlin organization(s): MachbarMacher
gábor hojtsy organization(s): Acquia
lennard westerveld volunteering
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.