Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
reg
dawehner
rogerrogers
jlongbottom
damien_vancouver
giorgio79
joakaune
HAg
imperator_99
Abelito
jillpadams
aagd
ladybug_3777
scotwith1t
andrezstar
phily
millionleaves volunteering
talisa1987
eigentor
ErnoVanhala
GuitarKat volunteering
mmlmitchell
dalemoore
chrisgross
brianbrarian
themusician organization(s): Western Washington University
carlygerard organization(s): Western Washington University
npacker
lendude organization(s): iO
mgifford organization(s): CivicActions
fjgarlin volunteering organization(s): Drupal Association
acbramley organization(s): PreviousNext
smustgrave organization(s): Mobomo
nicxvan
sanjadmin
kevinhbruce
stephen Piscura
travis-cunningham
danny englander
Dima DD
liam morland organization(s): University of Waterloo
chris matthews
laura.gates
robcarr
ehlovader
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.