Contribution records
Contributors

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

Give credit to everyone
Crell Crell
catch catch
scoutbaker scoutbaker
kbahey kbahey
yan yan
gaele gaele
cwgordon7 cwgordon7
sprugman sprugman
lilou lilou
c960657 c960657
webchick webchick
redndahead redndahead
add1sun add1sun
HansBKK HansBKK
Jaza jaza
cooperaj cooperaj
alexanderpas alexanderpas
adrian adrian
jjesus jjesus
tstoeckler tstoeckler
helpermedia Helpermedia
momper momper
guigui_nyc guigui_nyc
Sunshiney Sunshiney
seanburlington sean
kjunek kjunek
letapjar letapjar
jorap jorap
steveoliver steveoliver
fastballweb fastballweb
healycn healycn
pelicani pelicani
jenlampton jenlampton
wim leers wimleers
moshe weitzman weitzman
owen barton grugnog
damien tournoud damz
keith.smith keithsmith
dave reid davereid
wretched sinner - saved by grace wretched_sinner_saved_by_grace
gábor hojtsy goba
Pedro Lozano pl2
David D David_D
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.