Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
mrfelton
gregarios
xmarket
atan
skyredwang
drupalfan2
kerberos
lionstone
aacraig
beumont
heyyo
tonytosta
dlumberg
djbobbydrake
lyricnz
raghu_gh
vacilando
rp7
logi
jelo
cha0s
rade organization(s): Druid customer(s): Yle - Finnish Broadcasting Company
gobinathm volunteering organization(s): TATA Consultancy Services customer(s): Johnson & Johnson
bmunslow organization(s): SOCIETAT PORTAL DE LLEIDA S.L
goz organization(s): Centarro
donaldinou volunteering
sokru volunteering
loze
super_romeo
moehac
dave reid
eyecon-1
Oleksa-1
sense-design
Alex Andrascu
gaurav.goyal
chris matthews
marco-s organization(s): Namics
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.