Contribution records
Contributors

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

Give credit to everyone
danny_joris DannyJoris
bstoppel stoppel
srobert72 srobert72
jsims281 jsims281
chromaloop chromaloop
realityloop realityloop
JohnnyX JohnnyX
boztek boztek
ClearXS ClearXS
drewish drewish
johncionci johncionci
lawx01 lawx01
aspedia aspedia
giorgio79 giorgio79
dmcgrew dmcgrew
trickyricky26 trickyricky26
llbbl llbbl
trungonly trungonly
Macronomicus macrocosm
claar claar
darkknight7 darkknight7
madhusudan madhusudan
gumol gumol
careym86 careym86
btully btully
polmaresma polmaresma
Stan.Ezersky Stan.Ezersky
Déja Deja
tommy kaneko TommyKaneko
tea.time tea.time
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.