Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
webchick
rkerr
Steven
chx
STyL3
ramper
arosemartin
mudd
quicksketch
alexanderpas
geerlingguy
grobemo
dmitrig01
Bojhan
coltrane
yoroy
abhigupta
codesmith
mrfelton
sun
tobias
jstoller
barry_fisher
mnp
bevin
ISPTraderChris
kotnik
truyenle
zhgenti
renenee
mclinn
jbk_drupal
jenlampton
mautumn
rc2020
jnroche
rv0
mars80
mohammadjolani
raulmuroc
jwilson3
AmolB
PavanL
catch
aiphes
owen barton
boris mann
anders.fajerson
Mark B
david lesieur
damien tournoud
imre gmelig meijling
elijah lynn
tim.plunkett
drob
benjifisher volunteering organization(s): Harvard Web Publishing
rkoller
simohell organization(s): Druid
the_g_bomb organization(s): The University of Edinburgh
worldlinemine
quietone organization(s): Xequals
wardsky customer(s): Xequals
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.