Issue
Contribution records
Contributors

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

Give credit to everyone
RyanPrice
rfc2460
mindaugasd
manuelBS
yannickoo
sgb9809
fago
yenidem
SuperHoman
rooby
Karthick_s
vivdrupal
3cwebdev
abhijeetkalsi
earwax
kunago
kscheirer
stefank
presleyd
Amruta_dani
patchshorts
jbenezech
esolano
Heihachi88
jamesmorrish
balsama
aescudier
kiricou
patchygreen
jmuzz
FloriNet
gkaz
cassien
thentha18
t14
deeptanwar
yoshicn
deepakaryan1988 organization(s): Therefore
tondeuse
capysara
ram4nd volunteering
tim.plunkett
Gemma Morton
jason.fisher
k.skarlatos
geek-merlin
ludwig.rubio
sebastien m.
ovi.indrei volunteering
frank.schalkwijk
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.