Contribution records
Contributors

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

Give credit to everyone
aaron.hirtenstein aaron.hirtenstein organization(s): LocalGov Drupal
markconroy MarkConroy organization(s): The Confident customer(s): Big Blue Door, LocalGov Drupal
chrisgibson chrisgibson volunteering organization(s): Newcastle City Council
beautifulmind beautifulmind organization(s): Joshi Consultancy Services
awearring AWearring organization(s): North Kesteven District Council, West Lindsey District Council
stephen-cox stephen-cox organization(s): Agile Collective
wigglykoala WigglyKoala organization(s): Chicken customer(s): LocalGov Drupal
hannahdigidev hannahdigidev organization(s): Brighton & Hove City Council
rosie.catchpole rosie.catchpole organization(s): Brighton & Hove City Council
martin waite martin_waite organization(s): Webcurl Ltd
rupertj rupertj organization(s): Chicken customer(s): LocalGov Drupal
siliconmeadow siliconmeadow organization(s): Walsall Council customer(s): Walsall Council
rachael.keating@walsall.gov.uk rachael.keating@walsall.gov.uk organization(s): Walsall Council
tonypaulbarker tonypaulbarker
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.