Contribution records
Contributors

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

Give credit to everyone
rconstantine rconstantine
Jagg3d Jagg3d
michelle Michelle
deviantintegral deviantintegral
neilnz neilnz
3cwebdev setfree
goodeit goodeit
monotaga monotaga
csc4 csc4
Poieo Poieo
Shai Shai
asak asak
izmeez izmeez
will_in_wi willinwi
jrabeemer Giovanni_Glass
m_d_mcbride m_d_mcbride
cimb cimb
notarealperson notarealperson
BenK benk
donquixote donquixote
SeanBannister seanbannister
PRZ PRZ
shady_gun shady_gun
NewZeal newzeal
aren cambre arencambre
quinn-2 quinn-2
AmitV-2 AmitV-2
Craig Gardner cgardner
Parkes Design ParkesDesign
alan d. aland
avpaderno avpaderno volunteering
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.