Issue
Contribution records
Contributors

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

Give credit to everyone
ndf
borisson_ organization(s): Calibrate, Dazzle
joachim
johnwebdev
CountPacMan organization(s): ThinkShout
jummonk
icurk organization(s): Agiledrop - Your Trusted Drupal Teammates
merilainen organization(s): Mearra (formerly known as Wunder)
mpp
tomhollevoet organization(s): Calibrate
socketwench
josephdpurcell organization(s): Digital Bridge Solutions
stborchert organization(s): undpaul
strykaizer volunteering organization(s): ClicketyClick
miroslavbanov volunteering organization(s): JAKALA (formerly FFW)
grndlvl organization(s): GollyGood Software customer(s): Zivtech
tuwebo organization(s): Metadrop
dagomar
lapek
pfrenssen volunteering
recrit organization(s): Phase2
idebr organization(s): ezCompany
abu-zakham organization(s): Vardot
niko- volunteering
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.