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
dragos-dumi
inzo_
nils.destoop volunteering organization(s): iO
svendecabooter organization(s): Sven Decabooter customer(s): EntityOne, Dynamate
zhero - allam rachid
alexpott organization(s): Acro Commerce, Thunder
catch organization(s): Third and Grove
cilefen
jenlampton
larowlan organization(s): PreviousNext
longwave organization(s): Full Fat Things
mcdruid
poker10 organization(s): ActivIT s.r.o.
ram4nd
xjm organization(s): Zoocha, xjm
greggles organization(s): Colorado Governor's Office of Information Technology - Colorado Digital Service
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.