Issue
Contribution records
Contributors

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

Give credit to everyone
JvE organization(s): One Shoe
sun
catch
rob230
shnark
ptvv
mustanggb
wiifm
jamesdixon
bblake
jwilson3
webadpro
dooleysarahe
alauddin
swentel
andypost
alexpott
bradjones1
Jalandhar
David_Rothstein volunteering
bisonbleu
Shevchuk
dewalt volunteering
anybody volunteering
emmajane
guillaumev
mpdonadio
tistou
colan organization(s): Colan Schwartz Consulting
nithinkolekar
natanmoraes organization(s): CI&T customer(s): Pfizer, Inc.
netw3rker
blainelang
valthebald
stephesk8s
benjy organization(s): PreviousNext
star-szr
damien tournoud
das-peter
lachezar.valchev organization(s): JAKALA (formerly FFW)
i.bajrai
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.