Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
chx
tkoleary
plach
patrickd
thedavidmeister
dcrocks
neclimdul
rteijeiro
lewisnyman
timmillwood
cweagans
pancho
Bojhan
dries
joachim
tstoeckler
starchild
rootwork
kiphaas7
sphism
webchick
xjm
mallezie
oriol_e9g
jbrown
eaton
nod_
yoroy
ry5n
David_Rothstein
Homotechsual
mgifford
risse
alansaviolobo
markhalliwell
avpaderno volunteering
klonos organization(s): Backdrop CMS
saschaeggi volunteering
quietone volunteering
bertboerland volunteering
gisle organization(s): Hannemyr Nye Medier AS
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
serg2
gábor hojtsy organization(s): Acquia
moshe weitzman
kristen pol
tim.plunkett
Tor Arne Thune
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.