Contribution records
Contributors

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

Give credit to everyone
mortendk mortendk
FFFFFFFab FFFFFFFab
cdracars cdracars
mducharme mducharme
fragje fragje
pierrelord pierrelord
squiggy squiggy
Melissamcewen melissamcewen
August1914 August1914
modulist modulist
Prine Prine
betz betz
batigolix batigolix
suntog suntog
Mark_L6n Mark_L6n
ksoldink ksoldink
drupalninja99 jaykali
jenlampton jenlampton
johnatasJMO johnatasJMO
greg.1.anderson greg1anderson
hs@henrikstrindberg.se hs-at-henrikstrindberg.se
R.Hendel RalfHendel
Jeff Burnz jmburnz
david.mccandless david.mccandless
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.