Issue
Contribution records
Contributors

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

Give credit to everyone
casey
catch
bdragon
lilou
cburschka
dawehner
ajayg volunteering
erikwebb
lotyrin
yesct
kerasai
jrglasgow
zzrwood
joelpittet
jeanfei
kristiaanvandeneynde volunteering organization(s): Deeson
andyceo
David_Rothstein
msonnabaum
berdir
Crell
andypost
longwave
mgifford
dcam
donquixote
weri
sheldonkreger
hefox
ohthehugemanatee organization(s): Forum One
gifad
pounard
q0rban organization(s): Lullabot customer(s): Cisco Systems
colan organization(s): Colan Schwartz Consulting
mustanggb
mcdruid volunteering organization(s): Acquia
fabianx volunteering organization(s): Tag1 Consulting, Inc.
renatog organization(s): CI&T
izmeez
moshe weitzman
david strauss
tim.plunkett
oleg.medvedev
wim leers
ezra-g
Chris Charlton volunteering
Vergil.K
joseph.olstad
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.