Issue
Contribution records
Contributors

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

Give credit to everyone
klausi
Crell
catch
fabianx volunteering organization(s): Tag1 Consulting, Inc.
xen
pwolanin
effulgentsia
mpdonadio
webchick organization(s): Acquia
chx
xjm
dawehner
jhedstrom
larowlan
mikey_p
amateescu
znerol
yesct
aspilicious
attiks
arlinsandbulte
alexpott
neclimdul
sidharrell
rosk0 organization(s): Catalyst IT
mikeker
akki123
hkirsman
codebymikey organization(s): Zodiac Media
stephencamilo volunteering
greggles organization(s): Morris Animal Foundation
avpaderno volunteering
poker10 organization(s): ActivIT s.r.o.
selwynpolit
moshe weitzman
kim.pepper
damien tournoud
wim leers
tim.plunkett
geek-merlin
hass
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.