Contribution records
Contributors

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

Give credit to everyone
mooffie mooffie
mitchell mitchell
sirkitree sirkitree
quicksketch quicksketch
dgastudio kervi
ajayg ajayg
ngmaloney ngmaloney
mcarrera mcarrera
James_Stallings James_Stallings
mstrom81 mstrom81
joachim joachim
tommyk TommyK
drone drone
jayjaydluffy jayjaydluffy
bharata bharata
TomasBru TomasBru
ziccidus ziccidus
johnhorning johnhorning
mjross mjross
mas0h mas0h
torgospizza torgospizza volunteering
ivnish ivnish
tiago.gmarques tiago.gmarques
Andrew Gorokhovets AndrewGorokhovets
Orange Studio Orange_Studio
lunk rat LunkRat
Christopher Riley cmriley
morbus iff morbus
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.