Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rszrama organization(s): Centarro
keithm
TahitiPetey
hexabinaer
DeFr
joshmiller
bojanz
hyperglide
vasike
clashar
robcarr
vegantriathlete
w00zle
cvangysel
megansh
dpearcefl
watergate
akalata
nodecode
kaidjohnson
roderik
lmeurs
jlockhart
drclaw
ssoulless
Jaesin
dnotes
griz
ptmkenny
luco
zmove
adam1 volunteering
lingochad volunteering
MatthijsG
heddn organization(s): MTech, LLC
carrotandme
guypaddock organization(s): RedBottle Design, LLC customer(s): Inveniem
rkelbel48
sidharthap organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
timmillwood organization(s): Pfizer, Inc.
gngn organization(s): Computer Manufaktur GmbH
rahafrouz
Adam S
liam mcdermott
James A
i.bajrai
BenK
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.