Contribution records
Contributors

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

Give credit to everyone
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
duaelfr DuaelFr volunteering organization(s): Happyculture
mgifford mgifford organization(s): OpenConcept Consulting Inc.
milanpavic milanpavic
thenchev thenchev organization(s): MD Systems GmbH
ajits ajits volunteering organization(s): QED42
slashrsm slashrsm organization(s): MD Systems GmbH
pivica pivica organization(s): MD Systems GmbH
nod_ nod_ volunteering
sdstyles sdstyles organization(s): JAKALA (formerly FFW)
xjm xjm organization(s): Acquia
falufalump falufalump
droplet droplet
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
lendude Lendude volunteering organization(s): Noctilaris
mradcliffe mradcliffe organization(s): Kosada
helenasue helenasue organization(s): Lullabot
justafish justafish volunteering organization(s): Lullabot
runeasgar runeasgar volunteering
catch catch organization(s): Third and Grove
andrewmacpherson andrewmacpherson volunteering organization(s): Annertech
tim.plunkett tim.plunkett
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.