Contribution records
Contributors

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

Give credit to everyone
ultimike ultimike organization(s): DrupalEasy
volkswagenchick volkswagenchick organization(s): Kanopi Studios
mradcliffe mradcliffe organization(s): Kosada
rkoller rkoller
eadunn eadunn volunteering organization(s): WebNY - New York State Office of Information Technology Services
cindytwilliams cindytwilliams organization(s): Kanopi Studios
robincs RobinCS volunteering organization(s): ]init[ AG
smustgrave smustgrave organization(s): Mobomo
rpayanm rpayanm organization(s): Agileana
quietone quietone organization(s): PreviousNext
xjm xjm organization(s): Agileana
benjifisher benjifisher volunteering organization(s): FRUITION
ABElliott ABElliott organization(s): Agileana
blackbamboo BlackBamboo
shaal shaal volunteering organization(s): Phase2
my-family my-family organization(s): Squelle Group, s.r.o.
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.