Contribution records
Draft
Contributors

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

Give credit to everyone
tzandev tzandev organization(s): Bulcode
chrbak chrbak
blackiceua BlacKICEUA volunteering organization(s): Drupal Ukraine Community, Internetdevels
valic valic volunteering organization(s): FOREO customer(s): FOREO
edurenye edurenye organization(s): Digitalist
ytsurk ytsurk organization(s): Flash AG customer(s): Flash AG
phjou stargayte
jtriguero jtriguero organization(s): SDOS
spadxiii SpadXIII organization(s): Shift2
linkl linkl_git
jcnventura jcnventura organization(s): 1xINTERNET
idebr idebr organization(s): iO
ericvl EricVL
anneke_vde anneke_vde organization(s): iO
chewi3 ThomasJacobs
watergate MrWatergate organization(s): Sicse
shaxa ShaxA organization(s): Bulcode
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.