Contribution records
Contributors

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

Give credit to everyone
NickAT NickAT
emptyvoid emptyvoid
AdrianB AdrianB
artscoop artscoop
fugazi fugazi
Countzero Countzero
entrigan entrigan
servantleader servantleader
mfer mfer
spadron81 spadron81
Brentnauer Brentnauer
obrienmd obrienmd
andypanix andypanix
karens karens
arlinsandbulte arlinsandbulte
fmjrey fmjrey
kong kong
Hunabku Hunabku
thelocaltourist thelocaltourist
xjm xjm
joachim joachim
roderik roderik
gpk gpk
guillaumeduveau guix
damienmckenna damienmckenna organization(s): Current
design.er stefanriske
Coupon Code Swap undoIT
Josh Benner joshbenner
markus_petrux markuspetrux
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.