Issue
Contribution records
Contributors

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

Give credit to everyone
quicksketch
marrch_caat
tommyk
akalata
dinowonder
klonos
joostvdl
donquixote
amanire
xqi
HTF
Penidray
bbc
kingandy
RAFA3L
aubjr_drupal
mdorrell
stijndm
sammys
ldweeks
laroccadahouse
torrance123
jdanthinne
genjohnson
bjlewis2
jnettik
cmejo
nitrospectide
muriqui
dshields
markconroy
vaibhav_jadia
skyhawk669
carolineboivin
caspervoogt
rooby
petednz
wranvaud
mepperly
spokje organization(s): Annertech
j.slemmer
eric at nrd
ken hawkins
Renee S
Michael Zetterberg fd. Lopez
Martin Möhwald
Bruno-2M
prasannah.ganeshan
scott m. sanders
liam morland
stefan.schauer
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.