Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
mstef
dawehner customer(s): Drupal Association
klaasvw
ewandrews
rt3me
interdruper
jsacksick
joelpittet
alesr
quotesbro
rockaholiciam
zuernbernhard
lauriii organization(s): Druid
pefferen organization(s): Triquanta
ezeedub
khoatm
jadsay
JimJS
imshuffling
ak55
alimc29
cilefen
fox_01
loparr
usta
danielb
jelle_s
rkostov organization(s): JAKALA (formerly FFW)
siavash
marucci
andras_szilagyi
sgdev
chamilsanjeewa volunteering
wranvaud organization(s): Phase2
codefactory
mike.davis
boyan.borisov
steve.stotter
gregori.goossens
Harley Bussell organization(s): Flight Centre Travel Group
samuel.mortenson organization(s): Acquia
j-lee
A----
Martin. organization(s): ADM Interactive
no sssweat
michel.settembrino organization(s): European Commission and European Union Institutions, Agencies and Bodies
juanramonperez
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.