Issue
Contribution records
Contributors

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

Give credit to everyone
mxh volunteering organization(s): Hubert Burda Media
dakwamine organization(s): Eurelis
thalles organization(s): CI&T
rcodina
Webbeh organization(s): Georgia Institute of Technology
phjou
rosk0 organization(s): Catalyst IT
joachim organization(s): Factorial.io
smustgrave organization(s): Mobomo
andypost volunteering organization(s): Skilld
tobiasb volunteering organization(s): Gesellschaft zur Entwicklung von Dingen customer(s): OpenCulturas e.V.
_utsavsharma organization(s): OpenSense Labs customer(s): DrupalFit
larowlan organization(s): PreviousNext
fabiansierra5191 organization(s): Agileana
alexpott organization(s): Acro Commerce, Thunder
bnjmnm organization(s): Acquia
schlaukopf organization(s): Agileana
lauriii organization(s): Acquia
longwave organization(s): Full Fat Things
rpayanm organization(s): Agileana
xjm volunteering
ericgsmith organization(s): Catalyst IT
mpotter organization(s): Phase2
Aki Tendo
tim.plunkett organization(s): Acquia
ben.kyriakou organization(s): Cogapp
Jorge Navarro
mansi agarwal
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.