Issue
Contribution records
Contributors

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

Give credit to everyone
gmclelland
ericbroder
Grayside
hefox
drupal_was_my_past
bleen
damienmckenna
stovak
dkingofpa
codekarate
gdl
coderintherye
alberto56
jdleonard
nmc
fboulais
emackn
dealancer
betz
timbrandin
wjaspers
pianomansam
acouch
paulmckibben
richsky
kmonty
timaholt
pixelula
JvE
snipebin
patcon
alfthecat
andrewsuth
mpotter
spotzero
jemond
ThomasH
FreekVR
sherakama
joelpittet
eMuse_be
sgdev
david_garcia
scorchio
mustanggb
brunodbo
ibuildit
ronino
dobe volunteering
weynhamz organization(s): CI&T
suchdavid organization(s): Integral Vision Ltd
chipie
tanasi
donquixote
kalidasan
das-peter
Dean Reilly
dublin drupaller
chris.smith
rob c
claudiu.cristea organization(s): Webikon
darren oh volunteering organization(s): Software Paradigms International (SPI) customer(s): Estée Lauder Companies
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.