Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
mallezie organization(s): Mearra (formerly known as Wunder)
jibran volunteering organization(s): PreviousNext
benjy organization(s): PreviousNext
tstoeckler organization(s): bio.logis Genetic Information Management GmbH
dawehner volunteering
astringer
gantal organization(s): Elevated Third
vsujeetkumar organization(s): Material customer(s): Drupal India Association
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
sanjayk volunteering organization(s): Material customer(s): Drupal India Association
bobooon
joey91133 volunteering
b_sharpe organization(s): ImageX
quietone organization(s): PreviousNext
thtas
fgm organization(s): OSInet
anybody volunteering organization(s): DROWL.de
manuel garcia volunteering organization(s): Appnovation
wim leers volunteering
savkaviktor16@gmail.com organization(s): Skilld
isabelle.wagenvoord volunteering
jordan.jamous organization(s): Eighty Options
joachim 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.