Contribution records
Contributors

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

Give credit to everyone
akahn akahn
anantagati anantagati
dragonwize dragonwize
yang_yi_cn yangyicn
gunzip gunzip
asak asak
highvoltage highvoltage
joostvdl joostvdl
natuk avelios
guillaumeduveau guix
naught101 naught101
vacilando Vacilando
redndahead redndahead
virtualdrupal virtualdrupal
finex finex
adamo adamo
Miteto Miteto
djschoone djschoone
Tarsjusz Tarsjusz
andyf andy
pacome pacome
MamaGubs MamaGubs
kentr kentr
frankcarey frankcarey
adraskoy adraskoy
intyms intyms
udig udig
izmeez izmeez
pomliane Pomliane
birchy82 birchy82
momper momper
enkara enkara
Asaasco Asaasco
geshido geshido
scarvajal scarvajal
lomo LoMo
BigEd biged
ppcc ppcc
hey_germano sarah
mangus580 mangus580
JayFid JayFid
3dloco 3dloco
rickvug rickvug
jdln jdln
BenK benk
gmclelland gmclelland
anruether anruether
rwt rwt
mariomc mariomc
jason ruyle jasonruyle
rob c robc
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.