Issue
Contribution records

This contribution record is for a security advisory.

Contributors

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

Give credit to everyone
andrewbelcher organization(s): FreelyGive
dudleyc
tamasd
timwood
grevil organization(s): DROWL.de
japerry organization(s): Acquia
joevagyok organization(s): European Commission and European Union Institutions, Agencies and Bodies customer(s): European Commission and European Union Institutions, Agencies and Bodies
cilefen
damienmckenna volunteering
greggles organization(s): Colorado Governor's Office of Information Technology - Colorado Digital Service
mlhess
poker10 organization(s): ActivIT s.r.o.
xjm organization(s): Zoocha, xjm, QED42
andrew.wang organization(s): Ontario Digital Service
mparker17 organization(s): Consensus Enterprises customer(s): Ontario Digital Service
larowlan organization(s): PreviousNext
dench0
Git commit message
Commit types
  • 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

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.