Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
seaarg
alanpeart
kscheirer
j0rd
nod_ organization(s): Très Bien Tech
catch organization(s): Third and Grove
jstoller
donquixote
mpp
EJTH
attiks organization(s): Attiks
tedfordgif volunteering organization(s): WebFirst, Inc.
jenlampton organization(s): Jeneration Web Development customer(s): Backdrop CMS, Metropolitan Transportation Commission
douggreen volunteering organization(s): Peak Digital, LLC, Tag1 Consulting, Inc.
spokje volunteering
casey volunteering organization(s): SWIS
webdrips
larowlan organization(s): PreviousNext
anybody organization(s): DROWL.de
tunic organization(s): Metadrop
smustgrave organization(s): Mobomo
azinck organization(s): Forum One
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
geek-merlin organization(s): Geeks4Change, MachbarMacher
timohuisman organization(s): SWIS
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.