Issue
Contribution records
Contributors

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

Give credit to everyone
twod volunteering
taiger
sillo
mgifford
agerson
swim
picciuto
safaruque
mrP
gunwald
electricanimals
deggertsen
gregarios
fizk
greggmarshall
promes
rocketeerbkw
lahode
IreneKraus
profmikebroyles
ownage
bmango
cycas
stopshinal
dazz
streever
earthangelconsulting
FreeFox
courtlandwood
rv0
cuntryperson
smegnal
dehacker
Conlele
maki3000
dpearcefl
damienmckenna organization(s): Current
metzlerd
bunnicula
goose2000
giorgosk
dags
TerrorKiwi
rootwork
fugazi
johntang
mglaman
ocastle
ofry
KoshaK
schpinn
mikeohara
danielflippance
Morasta
wolffereast
nitrospectide
killua99
jurriaanroelofs
kikinakll
osopolar
jennypanighetti
inzor
dawitti volunteering
solerous
begrafx
duncan.moo
TDi-1
alan d.
Rdaneel-1
Lemon-Corner
Déja
sophie.sk
ling-drupal
ambient.impact volunteering
frank hh-germany
mstrelan
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.