Issue
Contribution records
Contributors

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

Give credit to everyone
sun
xurizaemon
SebCorbin
pierre_cotiniere
dawehner
aschiwi
jibran
lastar84
TelFiRE
snlnz
simg
nod_
pjcdawkins
klonos
giorgio79
alexweber
rooby
deanflory
askandlearn
wusel
joachim
izmeez
salvis
espirates
fenstrat
qqboy
gambry
skh
caschbre
raveendrab
fonant
hongpong
andypost volunteering organization(s): Skilld
saltednut organization(s): Acquia
awasson
pucowanje
bramvandenbulcke
chup
thalles organization(s): CI&T
Jeff Burnz
wim leers organization(s): Acquia
ñull
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.