Contribution records
Contributors

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

Give credit to everyone
OnkelTem onkeltem
dmstru dmstru
polom polom
emackn emackn
derhasi derhasi
Yuri Yuri
xaqrox xaqrox
twistor twistor volunteering
mtoscano mtoscano
dubs dubs
imclean imclean
jerenus Jerenus
pcambra pcambra
spuki spuki
bjcone bjcone
liquidcms liquidcms
msti msti
summit summit
meSte meSte
13rac1 eosrei
johan2 johan2
henkit henkit
franz franz
sphankin sphankin
Rosamunda Rosamunda
acouch acouch
HeathN HeathN
aimeerae aimeerae
brightbold brightbold
rcodina rcodina
cgdrupalkwk cgdrupalkwk
Niremizov Niremizov
barryvdh barryvdh
megachriz megachriz volunteering
jtsnow jtsnow
hargobind hargobind
mikeytown2 mikeytown2
stan turyn StanShevchuk
honza pobořil bobik
祥子 xiangzi
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.