Contribution records
Draft
Contributors

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

Give credit to everyone
JimmyAx jimmyax
Serjo Serjo
TimG1 TimG1
Orange Orange
7wonders 7wonders
rogical rogical
W32 W32
mohammed76 mohammed76
zkrebs zkrebs
dwalker51 dwalker51
benhelps benhelps
monican monican
RogueM RogueM
espirates espirates
alpp alpp
anarcat anarcat
invantix invantix
danielm danielm_git
marko3 marko3
AlexisWilke alexiswilke
stg11 stg11
hanno Hanno
mototribe mototribe
mgifford mgifford
uno uno
klonos klonos
cweagans cweagans
calte calvintennant
chaseontheweb ChaseOnTheWeb
carlhinton CarlHinton
jeremy Jeremy
geresy geresy
adammalone typhonius
avpaderno avpaderno volunteering
chegor chegor volunteering
Niklas Fiekas niklas
Dave Cohen yogadex2
Cray Flatline Cray_Flatline
laura s lauras
franz-m Franz-m
frank ralf frankralf
bartk lendrick
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.