Issue
Contribution records
Contributors

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

Give credit to everyone
tkoleary
saschaeggi
yoroy organization(s): Roy Scholten
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
rszrama organization(s): Centarro
alphex
rachel_norfolk organization(s): Open Development Ltd
delta
howdytom volunteering
duaelfr volunteering organization(s): Happyculture
Bojhan volunteering
eelkeblok organization(s): One Shoe
dipakmdhrm volunteering
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
imalabya organization(s): Valuebound
fgm organization(s): OSInet
xjm organization(s): Acquia
quietone organization(s): PreviousNext
gábor hojtsy organization(s): Acquia
star-szr volunteering organization(s): Northern Commerce
dom. volunteering organization(s): ACINO
manjit.singh organization(s): Material
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.