Contribution records
Contributors

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

Give credit to everyone
mitrpaka mitrpaka volunteering
brockfanning brockfanning
matslats matslats volunteering
rescandon rescandon organization(s): Four Kitchens
karlshea KarlShea
greenskin greenskin volunteering
nginex nginex customer(s): Dropsolid
junaidpv junaidpv organization(s): Detlus customer(s): Wickwood Marketing
thatguy thatguy organization(s): Siili Solutions
lysenko LHVR volunteering organization(s): DevBranch, Drupal Ukraine Community
drupalam ameshkin volunteering
anybody Anybody organization(s): DROWL.de
pcate PCate
geek-merlin geek-merlin organization(s): Geeks4Change, MachbarMacher
it-cru it-cru
Git commit message
Commit types
  • 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

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.