Issue
Contribution records
Contributors

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

Give credit to everyone
bcmiller0
deekayen
frankcarey
attiks
erikwebb
e2thex
thedavidmeister
alfaguru
blazindrop
Enxebre
drkloc
aohrvetpv
matt2000
acbramley
eelkeblok organization(s): One Shoe
flyke
mikemadison organization(s): Pacific Northwest National Laboratory
valthebald organization(s): JAKALA (formerly FFW)
tunprog volunteering
fubarhouse
marlonleandropereira volunteering organization(s): CI&T
loopduplicate organization(s): Hook 42 customer(s): SunPower Corporation
liampower organization(s): Reading Room
sumthief volunteering organization(s): DrupalJedi
kristiaanvandeneynde organization(s): Deeson
IRuslan volunteering organization(s): DrupalJedi
jvdkolk
rosk0 organization(s): Catalyst IT customer(s): Land Information New Zealand
Bußmeyer
john cook organization(s): Curve Agency
david.lukac organization(s): i-KOS
matt v. 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.