Issue
Contribution records
Contributors

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

Give credit to everyone
keesje
micahw156
silurius
vijaycs85
dhalbert
bezu60
lias
Immansophia
pjbarry21
Miao1994
DebMorris
hwasem
_Arjan_
bneil
tzt20
bigdogsam
PascalAnimateur
sebaz
schifazl
BlaF
drupalerocant
Lostboy22
jasonkryst
davidkp
michelle
ladybug_3777
happysnowmantech
akalata
leistiko_texvet
Jen7
Funksmaname
tajindersingh
sirian
idea_vasil
pcrats33
katannshaw volunteering
liquidcms
debain
veverita
maletruv
pgdagenais
jackalope
cdmo
ryanoreilly
savingstrangers
susoson
rbrownell
miniwebs2
klidifia
Gib...
enzo de simone
didier misson
mprell
Keith Caulkins
.bert
Steve -cc
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.