Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
bkildow
myers_d
EndyBoooj
marcushenningsen
wojtha
picco
hefox
jameria21
fabianx volunteering organization(s): Tag1 Consulting, Inc.
rjbrown99
atlea
Fidelix
chaseontheweb
amanaplan
corvus_ch
firebird
steinmb volunteering
gunwald
kristygislason
dasjo
bowersox
lobsterr
sch4lly
lzimmerman
boshtian
janusman
vinmassaro
rwohleb
jongagne
wfyanmnm
nmillin
badrange organization(s): Mearra (formerly known as Wunder)
grzesag
slydevil
dgtlmoon
hurricane66
verres
oranges13
paolomainardi
steven jones
cameron tod
josh waihi organization(s): Acquia
Delphine Lepers organization(s): Trasys customer(s): European Commission and European Union Institutions, Agencies and Bodies
hass
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.