Contribution records
Contributors

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

Give credit to everyone
dawehner dereine volunteering
duaelfr DuaelFr volunteering organization(s): Happyculture
drubb drubb volunteering
arla arla organization(s): MD Systems GmbH
swentel swentel
xjm xjm organization(s): Acquia
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
berdir berdir organization(s): MD Systems GmbH
lokapujya lokapujya
justachris christopherG organization(s): Bounteous
agentrickard agentrickard organization(s): Palantir.net
chx chx organization(s): Migrate Rocks, Smartsheet
toncic toncic organization(s): MD Systems GmbH
eiriksm eiriksm organization(s): Ny Media AS
soul88 Soul88
bojanz bojanz organization(s): Centarro
mikeegoulding mikeegoulding organization(s): Ashday Interactive Systems
ginovski Ginovski organization(s): MD Systems GmbH
slimbk slimbk
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.