Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rosk0 organization(s): Catalyst IT
xurizaemon organization(s): Catalyst IT
jweowu organization(s): Catalyst IT
bzrudi71 volunteering
andypost volunteering organization(s): Skilld
pounard
amateescu customer(s): Pfizer, Inc.
catch organization(s): Third and Grove
TomGould01 volunteering
daffie organization(s): Finalist
sylus
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
ramadan35 volunteering
samlerner organization(s): CivicActions customer(s): Centers for Medicare and Medicaid Services
larowlan organization(s): PreviousNext
poker10 organization(s): ActivIT s.r.o.
alexpott organization(s): Acro Commerce, Thunder
kopeboy volunteering
bradjones1 organization(s): Not Vanilla, Inc., OPTASY customer(s): Drupal Association
koolaidguy
mparker17 organization(s): Consensus Enterprises customer(s): Ontario Digital Service
mradcliffe volunteering
rob.barnett volunteering
bappa.sarkar organization(s): Weight Watchers
emircanerkul
dydave volunteering organization(s): Code Enigma
berdir organization(s): MD Systems GmbH
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.