Contribution records
Contributors

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

Give credit to everyone
dman dman
roxtaz roxtaz
ainigma32 ainigma32
gantenx gantenx
crutch crutch
mmilo mmilo
RWWood RWWood
Ashford Ashford
naheemsays nbz
Nodin Nodin
OldAccount lrobeson
jsm174 jsm174
janusman janusman
BigEd biged
mattyoung mattyoung
buckley buckley
jurgenhaas jurgenhaas
farald farald
marcoBauli marcobauli
kentr kentr
mattez mattez
dipole dipole
lias lias
casey casey
adrianmak adrianmak
wgrunberg wgrunberg
sitorush sitorush
alex_stanhope alex_stanhope
david stosik davidstosik
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.