Contribution records
Contributors

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

Give credit to everyone
klausi klausi
sutharsan sutharsan
jeroenbegyn jeroenbegyn organization(s): SQLI - Belgium
tomasnagy tomasnagy volunteering organization(s): SQLI - Belgium
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
kristiaanvandeneynde kristiaanvandeneynde organization(s): Deeson
zeip ZeiP volunteering organization(s): Citrus Solutions Oy
jofitz jofitz organization(s): ComputerMinds
fellaroon fellaroon volunteering
alexpott alexpott organization(s): Acro Commerce, Thunder
mondrake mondrake volunteering
catch catch organization(s): Third and Grove
sokru kallevu volunteering
lauriii lauriii organization(s): Acquia
xjm xjm organization(s): Acquia
krzysztof domański krzysztof_domanski organization(s): abventor
tim.plunkett tim.plunkett organization(s): Acquia
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.