Issue
Contribution records
Contributors

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

Give credit to everyone
vikingew
robhamm
aspilicious
yktdan
guidot
dboulet
bfroehle
hvang
eeyorr
zilverdistel
cyberwolf
nancydru
mermentau
j0rd
docwilmot
joekrukosky
sun
robcarr
fonant
grossmann
izmeez
Crell
jox
endiku
mrothmay
bryanhidalgo
gagoo
jackalope
webdevana
pauljr8
Carnix
paulgemini
sveldkamp
dropbydrop
matthewv789
Maitane77
adf1969
liquidcms
catch organization(s): Third and Grove
xjm
eigentor
SeanA
raphar
heddn
jtherkel
webchick
dries
David_Rothstein volunteering
3cwebdev
jlea9378
aohrvetpv
mattshoaf
tfink
pranav45 organization(s): OSSeed Technologies
makbul_khan8 volunteering organization(s): Cognizant Technology Solutions
akshita
Fredsvanelli
kellyimagined
WH Hammond
Andrew Schulman
dave kopecek
Michael-IDA
ar-jan
nicolas bouteille
IT Munger
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.