Issue
Contribution records
Contributors

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

Give credit to everyone
ivanbueno
blakehall
alex_b
ericduran
pcambra
jelle_s
shaundychko
jackbravo
reecemarsland
tema
andypost volunteering organization(s): Skilld
mvc
sir_squall
tommyk
okokokok
mpv
beatnikdude
exeapps
twistor volunteering
attheshow
markwk
patcon
4alldigital
markabur
mikran organization(s): Mediamaisteri Oy
jurriaanroelofs
wutu
queenvictoria
micromegas
j0rd
mparker17
kenorb
jmichelgarcia
johnennew
dbassendine
megachriz volunteering organization(s): WebCoo
joelpittet
mglaman
goldii
forestmars
dillix
ysaid volunteering
laVera volunteering
johnny5th organization(s): Encore Multimedia
csakiistvan
kebne
cmarcera
eiriksm organization(s): Ny Media AS
controla
grahamc organization(s): Webcurl Ltd
jerry volunteering
g33kg1rl
jm_drupal
nwom
tedwyer
brad.bulger
clemens.tolboom
lunk rat
Jason Dean
-enzo-
agnese.stelce
alan-ps
b-prod
bès organization(s): Happyculture
aron novak
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.