Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
dawehner
chalk organization(s): DrupalSquad
mfernea organization(s): AmeXio Fuse
loopduplicate organization(s): Hook 42
oadaeh organization(s): Hook 42
mmrares organization(s): AmeXio Fuse
miroslavbanov volunteering organization(s): JAKALA (formerly FFW)
vinmassaro
renguer0 volunteering
joegraduate organization(s): The University of Arizona
steven jones organization(s): ComputerMinds
damien tournoud
kristen pol organization(s): Hook 42
stefan.r
ludo.r
liam morland volunteering organization(s): Scouting Waterloo Region, University of Waterloo
kim.pepper organization(s): PreviousNext
smustgrave organization(s): Mobomo
mohit_aghera organization(s): PreviousNext
alexpott organization(s): Acro Commerce, Thunder
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.