Issue
Contribution records
Contributors

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

Give credit to everyone
Volx
megachriz
jaydarnell
aoturoa
bsarchive
kolier
genjohnson
Yuri
guillaumev
Mazzhe
roball
drupalninja99
jpstrikesback
nithinkolekar
mustanggb
antoinetooley
smurfxx
dobe
apmsooner
howards
schifazl volunteering
plong0
hansfn
liquidcms
haggins
skadu
alphawebgroup
biswajeetparida
OliverColeman
shaisamuel
sonicthoughts volunteering
mkolar
tchopshop
stiknoltz volunteering
weri organization(s): Previon Plus AG
maxplus
skylennard
junaidpv organization(s): Detlus customer(s): Wickwood Marketing
nwom
joewhitsitt
nimek volunteering
Collins405
sarvab
joelpittet
karlshea
robertgarrigos
spotzero organization(s): Coldfront Labs Inc.
hgoto volunteering
eaglegamma volunteering
w01f
off
swilmes
geek-merlin
k.skarlatos
alain dg
pontus.froden
daro.pl
joshua.boltz
eugene.ilyin volunteering organization(s): DrupalJedi
design.er
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.