Issue
Contribution records
Contributors

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

Give credit to everyone
joachim
icecreamyou
drewish
yesct
hexengon
AaronCollier
dngpng
bajakan
deviantintegral
Ryanbach
wmn
shrop
rcarvalho
Hetta
sampeckham
miiimooo
geraldito
jonesui
valentino_42
mark_basedow
jerror
JThan
prbass
krlucas
SpriteGF
schlotterich
sun
AmrMostafa
skyredwang
MGN
Ylan
andypost
rayray
nquocbao
irishgringo
pillarsdotnet
codeseek
bcn
clo75
loze
juliekj
dmetzcher
ppmax
pildwell
robertdjung
gorcon
thijsvdanker
zdean
gregorovius
Fayna
drupal999
seidren
timatlee
nstrassner
manoz_79
peterjmag
hebhansen
Encarte
mean0dspt
jubalkessler
geerlingguy
strndy
HS
andribas
kevinquillen
twod
iNade
DjC4
summit
jimmb
R.Muilwijk
Flying Drupalist
tom friedhof
Aaron Stanush@drupal.org
greggus-1
TRs-1
aren cambre
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.