Contribution records
Draft
Contributors

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

Give credit to everyone
msonnabaum msonnabaum
arthurf arthuregg
henrikakselsen henrikakselsen
batje batje
jordanmagnuson JordanMagnuson
basvredeling basvredeling organization(s): Code Culture
oliverpolden xalen
geerlingguy geerlingguy
nbucknor nbucknor
thlafon thlafon
b_man B_man organization(s): Drupal Association
markusd1984 markusd1984
mw4ll4c3 mw4ll4c3
ptmkenny ptmkenny
ankithashetty AnkShetty volunteering organization(s): Specbee customer(s): Drupal India Association
andypost andypost volunteering organization(s): Skilld
mortona2k mortona2k volunteering
josh waihi fiasco
shiraz dindar Shiraz
dom. Miroslav volunteering organization(s): ACINO
joseph.olstad joseph.olstad
philipnorton42 philipnorton42
tfranz tfranz organization(s): JAKALA (formerly FFW)
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.