Contribution records
Contributors

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

Give credit to everyone
norrab2 norrab2
LukeLast lukelast
bennybobw bennybobw
vildmule vildmule
ouzo ouzo
mac_perlinski macperlinski
nrasmus nrasmus
oadaeh oadaeh
jsm174 jsm174
melon melon
axle_foley00 ylynfatt
redben redben
jacerider JaceRider
liquidcms liquidcms
sinedv sinedv
a_c_m acm
gustav delius
magnus Magnus
eliosh eliosh
martinkrupicka martinkrupicka
yang_yi_cn yangyicn
dkruglyak dkruglyak
StephenFresh StephenFresh
fabio84 fabio84
srjosh srjosh
Mark_Watson27 Mark_Watson27
sutharsan sutharsan
johngriffin johngriffin
franz franz
TripleEmcoder TripleEmcoder
luckysmack luckysmack
itserich itserich
allie micka vauxia
mike stewart mdrmike
challa.kamal challakamal
kristen pol kepol
neha.jaha neha.jaha
simonp-1 simonp-1
mishhh mishhh
danielkorte danielkorte
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.