Contribution records
Contributors

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

Give credit to everyone
rodrigoaguilera rodrigoaguilera
hellomobe hellomobe
athens72 athens72
Letharion Letharion
fago fago
waverate waverate
salientknight salientknight
wjaspers wjaspers
softmax softmax
rfay rfay
berenddeboer berend
willieseabrook willieseabrook
bitsgrecco bitsgrecco
OldAccount lrobeson
tripper54 tripper54
brightbold brightbold
skilip skilip
geerlingguy geerlingguy
nfriend nfriend
haggster haggster
RKS RKS
kifuzzy kifuzzy
foroysund foroysund
tommychris TommyChris
petarb PetarB
bisonbleu bisonbleu
anavarre anavarre
droz72 droz72
earthangelconsulting goatvirus
drzraf drzraf
FreeFox FreeFox
mitchell mitchell
trilok trilok
drupaletteiz drupaletteiz
sjazaerli sjazaerli
firfin firfin
_grizly _grizly
xurizaemon xurizaemon
end user end_user
rakesh.gectcr rakeshjames
Git commit message
Commit types
  • 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

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.