Contribution records
Contributors

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

Give credit to everyone
rdeboer rdeboer
modusmg modusmg
randallknutson randallknutson
nancygill nancygill
mmtt mmtt
edb edb
quicksketch quicksketch
pmackay pmackay
mattsmith3 mattsmith3
mvc mvc
AlxVallejo AlxVallejo
mr_scumbag mr_scumbag
kerberos kerberos
javijevi javijevi
puddyglum Puddyglum
nattyweb NattyWebDev
basvredeling basvredeling organization(s): Code Culture
osman osman volunteering
elstudio elstudio
jweirather jweirather
phil.stphns phil.stphns
luk.stoops luk.stoops
simon georges simongeorges organization(s): Makina Corpus
jon.skn3 jon.skn3
hawkeye.twolf derek.deraps organization(s): Current
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.