Issue
Contribution records
Contributors

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

Give credit to everyone
awm organization(s): Johnson & Johnson
trevorbradley
emek organization(s): Lund University
kbrodej organization(s): Agiledrop - Your Trusted Drupal Teammates
dww volunteering
matthiasm11 organization(s): Randstad Digital
ezeedub organization(s): Phase2
nace_fr organization(s): Agiledrop - Your Trusted Drupal Teammates
vpeltot organization(s): Niji
ngkoutsaik organization(s): Agiledrop - Your Trusted Drupal Teammates
s3b0un3t volunteering
szhu organization(s): Consensus Enterprises customer(s): Health Canada - HPFB
maursilveira organization(s): Northern Commerce
mparker17 organization(s): Consensus Enterprises customer(s): Health Canada - HPFB
colan organization(s): Consensus Enterprises customer(s): Health Canada - HPFB
guilhermevp organization(s): CI&T
featherbelly volunteering organization(s): KOMOKO Ltd
rajeshreeputra volunteering organization(s): Acquia, Shivswarajya Inc. customer(s): Shivswarajya Inc.
Webbeh organization(s): Georgia Institute of Technology
coaston
uceap-web
nicolas s.
stefan.korn organization(s): Stefan Korn - Webentwicklung
tim-diels organization(s): Calibrate
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.