Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
slashrsm organization(s): MD Systems GmbH
pguillard
seanb
willyk
phenaproxima organization(s): Acquia
marcoscano organization(s): Lullabot customer(s): Acquia
naveenvalecha volunteering
tstoeckler organization(s): bio.logis Genetic Information Management GmbH
mallezie organization(s): Mearra (formerly known as Wunder)
larowlan organization(s): PreviousNext
dawehner volunteering
Bojhan volunteering
yoroy organization(s): Roy Scholten customer(s): Dropsolid
effulgentsia organization(s): Acquia
xjm organization(s): Acquia
rikki_iki
amateescu customer(s): Pfizer, Inc.
acbramley organization(s): PreviousNext
jibran
GrandmaGlassesRopeMan organization(s): Acquia
webchick organization(s): Acquia
leslieg volunteering
sam152 volunteering organization(s): PreviousNext
emb03
siavash
vacho organization(s): Skilld
maskedjellybean volunteering
vsujeetkumar organization(s): Material customer(s): Drupal India Association
andypost volunteering organization(s): Skilld
wim leers organization(s): Acquia
chr.fritsch organization(s): Thunder
suranga.gamage volunteering
geek-merlin organization(s): Geeks4Change, MachbarMacher
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.