Issue
Contribution records
Contributors

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

Give credit to everyone
tyr
arlinsandbulte
oggsmith
gribnif
ssemigr
butler360
karens
chrixix
kuopionkiipeilyseura
fmesco
hchall
bomarmonk
itserich
tigron
droath
tuphill
thebuckst0p
mdpenguin
SaxxIng
awolfey
ophelia
nickgee
izmeez
jamesialford
baff
DeFr
akolahi
darrellduane
thlor
ambereyes
btmash
iantresman
hbananda
kruser
noah
reserve
inforeto
sonicthoughts
spydmobile
bneel
roball
quixxel
agill
Fr0s7
rickyd1
webscape
nlambert
chadchandler
jpcwebb
jsenich
radj
jmseigneur
sdsheridan
davemaxg
cabplan
rj
xingchong
crimsondryad
omerida
reaneyk
vulfox
dgtlmoon
anektod
gthing
dmurkerson
span
stella
mrothmay
bootstrapjohnny
brewern
rhibbitts
erikhopp
drm
raven_web
e-fee
Tony Sharpe
Liam Mitchell
Dave Hirschman
ahmed.sajid
tyler.frankenstein
james marks
Rino-1
tragic.rich
gaëlg
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.