Contribution records
Contributors

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

Give credit to everyone
lpalgarvio LPCA
servantleader servantleader
roam2345 jucallme
pcambra pcambra
BenK benk
mgifford mgifford
bigdave bigdave
combicart combicart
mattbk mattbk
hexabinaer hexabinaer
dawehner dereine
WilliamV WilliamV
danny_joris DannyJoris
klonos klonos
wpanssi wpanssi
helmo helmo
drupa11y marcus.morba
Seraphin42 Seraphin42
rmiddle rmiddle
seanberto seanberto
artatac artatac
marcusx marcusx
hgurol hgurol
robloach robloach
hunziker hunziker
cesareaugusto cesareaugusto
apolitsin apolitsin
likewhoa likewhoa
damienmckenna damienmckenna
infines infines
MPeli MPeli
webankit babbar.ankit
nzcodarnoc nzcodarnoc
Floop Floop
ambereyes ambereyes
bryancasler animelion
Kreapix Kreapix
IWasBornToWin IWasBornToWin
rockclimb rockclimb
neclimdul neclimdul
ced.cornez ced.cornez
Katrina B Katrina B
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.