Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
berdir organization(s): MD Systems GmbH
anybody organization(s): DROWL.de
cgoffin organization(s): Sopra Steria
szantog organization(s): Momentum Mozgalom
sorlov organization(s): Skilld
andypost volunteering organization(s): Skilld customer(s): Devalma
dqd volunteering organization(s): MAROQQO studios
weseze volunteering
danharper volunteering organization(s): hrpr
bgilhome
edison08 organization(s): Aïon Solutions
mlncn organization(s): Agaric customer(s): Drutopia, Portside
dimKarp
penyaskito volunteering organization(s): Lullabot
lisagodare volunteering
carsoncho organization(s): Forum One
AlGab
reinfate organization(s): DevBranch, Drupal Ukraine Community
bluegeek9 volunteering
das-peter organization(s): Cando
louis-cuny organization(s): Aïon Solutions
b-prod organization(s): Aïon Solutions
den tweed
liam morland volunteering organization(s): OpenPlus, Scouting Waterloo Region
jastraat organization(s): CivicActions, Centers for Medicare and Medicaid Services customer(s): Centers for Medicare and Medicaid Services
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.