Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
JHeffner
scor volunteering
a6hiji7
bfroehle
betamos
marcingy
attiks
sun
geerlingguy
traviscarden volunteering
mbaynton volunteering
osman volunteering
catch organization(s): Third and Grove
johnwebdev
icgurney
anrikun
xjm organization(s): Acquia
eiriksm organization(s): Foreningen Drupal Norge, Ny Media AS, Violinist
bkosborne organization(s): Princeton University
quietone volunteering
mxr576 organization(s): Pronovix
tgoeg
larowlan organization(s): PreviousNext
pameeela
partyka organization(s): Princeton University
jp.stacey
robin monks
dave reid
lars toomre
kim.pepper organization(s): PreviousNext
james.williams organization(s): ComputerMinds
wim leers organization(s): Acquia
Git commit message
Commit types
  • 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

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.