Contribution records
Contributors

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

Give credit to everyone
arthurf arthuregg
cor3huis cor3huis
patcon patcon
OnkelTem onkeltem
jlporter jlporter
Jackinloadup Jackinloadup
SB SB
greenskin greenskin
majortom majortom
kika kika
jeffwidman jeffwidman
kbasarab kbasarab
mfb mfb
hongpong HongPong
ezeedub ezeedub
sectionz sectionz
webankit babbar.ankit
dark11star dark11star
Leeteq Leeteq
pillarsdotnet pillarsdotnet
drupa11y marcus.morba
Rob_Feature bobchristenson
dilari dilari
ccshannon ccshannon
tripper54 tripper54
mrfelton mrfelton
chemicalroman chemicalroman
kobnim kobnim
etiennechataignier echataig
iva2k iva2k
damienmckenna damienmckenna
Andy B Andy B
mail@victorquinn.com victorquinn
rob c robc
agence web coheractio CoherActio
simon georges simongeorges
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.