Issue
Contribution records
Contributors

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

Give credit to everyone
colan
nguyentran
philipz
travismiller
mrfelton
biigniick
Quarath
jlholmes
samw
jeffschuler
rooby
alexmc
mmasotti
madeby
flynorc
nfavrod
raystin
enap
rsgracey
gaele
vregouby
ambientdrup
sea4
r2integrated
guile2912
bradjones1
giorgio79
jrao
Timusan
MTecknology
tky
rnield
aeava
argo27
epineda
dankoB
emjayess
kingswoodute
haydeniv
basvredeling
Masterfool
Lumis
ranavaibhav
Leeteq
anas_maw organization(s): Vardot
rcodina
schnydszch
ajinkya.naik
Norberto Ostallo
lunk rat
shiraz dindar
damien tournoud
dan carlson
gaëlg
asgar.ahmed
ar-jan volunteering
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.