Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
alanoakden organization(s): Access (now GAIN)
pameeela
smustgrave organization(s): Mobomo
lauriii organization(s): Acquia
shree0007
mradcliffe volunteering
cecelias volunteering
drupak volunteering
tanzeel volunteering
veades volunteering
hktang
skachenkov volunteering
deivalko
joshmiller organization(s): Urban Institute
luismagr volunteering organization(s): Code Enigma
vijayavelr volunteering organization(s): CTG
xjm organization(s): HeroDevs, OPTASY, xjm, Zoocha
sindicatoespx
anybody organization(s): DROWL.de
liquidcms
carolpettirossi organization(s): ImageX
dimitriskr organization(s): Point Blank
maskedjellybean
joaopauloc.dev organization(s): ImageX
simon-p volunteering
p-neyens organization(s): Sopra Steria customer(s): Belgian FPS Policy and Support (BOSA)
phernand42
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.