Contribution records
Contributors

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

Give credit to everyone
yched yched
anruether anruether
btmash btmash
joachim joachim
TripX TripX
kehan kehan
mmgg mmgg
matrobin matrobin
ddiakopoulos ddiakopoulos
MarkFischer MarkFischer
aspilicious aspilicious
christefano christefano
webchick webchick
dreadlocks1221 dreadlocks1221
sashdo sashdo
dkh dkh
ccoppen ccoppen
ultimateboy ultimateboy
chx chx
catch catch
dasjo dasjo
realityloop realityloop
theamoeba theamoeba
jenlampton jenlampton
jbrown jbrown
theborg theborg
xjm xjm
dotman dotman
aron novak aronnovak
lars toomre ltoomre
damien tournoud damz
mike stewart mdrmike
kevin hankens kevinhankens
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.