Contribution records
Contributors

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

Give credit to everyone
nancydru nancyw
markDrupal markdrupal
karens karens
jonathan1055 jonathan1055
merlinofchaos merlinofchaos
damienmckenna damienmckenna
webchick webchick
d0t101101 d0t101101
bendiy bendiy
Azol Azol
pimousse98 pimousse98
spydmobile spydmobile
achton achton
indigoblue indigoblue
3dloco 3dloco
cyberwolf Cyberwolf
rconstantine rconstantine
zilverdistel zilverdistel
lsolesen lsolesen
thomsol thomsol
bartl bartl
ParisLiakos rootatwc
bvanmeurs bvanmeurs
faboulaws faboulaws
anybody Anybody
asauterChicago asauterChicago
kenorb kenorb
bird-cage bird-cage
Todd Young ToddYoung
tim.plunkett tim.plunkett
mark trapp itafroma
liam morland lkmorlan
Git commit message
Commit types
  • 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

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.