Contribution records
Contributors

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

Give credit to everyone
merlinofchaos merlinofchaos
bensnyder bensnyder
vj0914 vj0914
deviantintegral deviantintegral
gausarts gausarts
mooffie mooffie
fit fit
theabacus theabacus
mitjaxp mitjaxp
blackdog blackdog
liquidcms liquidcms
tjb74 tjb74
SuperRookie SuperRookie
leovarg leovarg
Rob_Feature bobchristenson
brynbellomy brynbellomy
dawehner dereine
dravidian7 dravidian7
CccXxx CccXxx
RichieRich RichieRich
BeaPower BeaPower
awm6392 awm6392
yaworsk yaworsk
glennnz glennnz
mossill mossill
henriquefm henriquefm
frozen10 frozen10
tmwagner TWagner
rfiertek rfiertek
kerios83 kerios83
manoloka manoloka
dunx dunx
juanjo_vlc juanjo_dv
marcopanichi marcopanichi
thumbslinger thumbslinger
Matthew Davidson mjd
Archie Bunker Archie Bunker
Silicon.Valet Silicon.Valet
Marko B MarkoBx
Rob T Rob_T
anne-pierre Anne-Pierre
Jerome F Jerome F
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.