Contribution records
Draft
Contributors

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

Give credit to everyone
lor lor
YK85 YK85
bunker bunker
xjm xjm
ChaosD ChaosD
rburgundy rburgundy
deltab deltab
kenorb kenorb
blisteringherb morgan.rich
theshanergy deckfifty
clashar clashar
zazinteractive zazinteractive
phayes phayes
fourmi4x fourmi4x
tpfeiffer tpfeiffer
kgeographer kgeographer
xtfer xtfer
rootwork rootwork
domdest domdest
xaa xaa
NenadP NenadP
chey chey
Flying Drupalist Flying_Drupalist
robby.smith robby.smith
viren.ratan viren.ratan
ccshannon ccshannon
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.