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
xjm organization(s): Acquia, xjm
catch organization(s): Third and Grove
dries
webchick organization(s): Acquia
effulgentsia organization(s): Acquia
phenaproxima organization(s): Acquia
naveenvalecha volunteering
colan organization(s): Colan Schwartz Consulting
yoroy organization(s): Roy Scholten
marcoscano volunteering organization(s): Lullabot customer(s): Acquia
seanb
andypost volunteering organization(s): Skilld
woprrr volunteering organization(s): NeoLynk
kurtfoster organization(s): Department of Premier and Cabinet - Victoria, Australia
yannisc organization(s): Netstudio
balsama organization(s): Acquia
gargsuchi organization(s): Salsa Digital customer(s): Department of Premier and Cabinet - Victoria, Australia
berdir organization(s): MD Systems GmbH
codechefmarc
andrewmacpherson volunteering
alison volunteering
volkswagenchick organization(s): Kanopi Studios
quietone organization(s): PreviousNext
gábor hojtsy organization(s): Acquia
wim leers volunteering organization(s): Acquia
geek-merlin organization(s): MachbarMacher
chr.fritsch organization(s): Thunder
Christopher Riley
chris matthews
sealionking
Git commit message
Commit types
  • 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

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.