Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
tcalin
JamesSharpe
Leeteq
alanburke
Poieo
jaymcgraw
fago
13rac1
gmak
mrmeech
Fannon
Woggers
steinmb volunteering
darrellduane
chirale
rooby
codycraven
aimeerae
nancydru
koppie
loophole080
ikeigenwijs
rwilson0429
maxplus
darrell_ulm volunteering
clintu
bburg organization(s): Forum One
npacker
mtdaveo
wizonesolutions volunteering organization(s): WizOne Solutions
natanmoraes organization(s): CI&T customer(s): Pfizer, Inc.
richardp
dave reid
alain dg
kristen pol
elijah lynn
David Hernández
norman.lol
kurund
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.