Contribution records
Contributors

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

Give credit to everyone
jjchinquist jjchinquist organization(s): drunomics, Drupal Austria
al3nka al3nka organization(s): acolono GmbH
antonellasevero antonellasevero
bletch bletch
dan2k3k4 dan2k3k4 organization(s): amazee.io customer(s): amazee.io
drupalviking drupalviking volunteering organization(s): Um ad gera ehf.
volkswagenchick volkswagenchick volunteering
drale01 drale01
emma horrell emma-horrell organization(s): The University of Edinburgh
jct321 JCT321 volunteering organization(s): Salsa Digital
Metalviking fransi
nicoloye nicoloye volunteering organization(s): Smile
useernamee useernamee organization(s): drunomics
zoocha will ZoochaWill organization(s): Zoocha
fago fago organization(s): drunomics
pemoze pemoze
astbabs astbabs volunteering
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.