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
0xhamy
ama62
askibinski
ayalon organization(s): Liip
betah4k
gabesullice
jm.liip
john morahan
michaelwinser
nbanderson
offensive-ai
plach organization(s): Tag1 Consulting, Inc.
qquynh
unknownhad
larowlan organization(s): PreviousNext
longwave organization(s): Full Fat Things
mcdruid organization(s): Acquia
phenaproxima organization(s): Acquia
seanb
benjifisher volunteering organization(s): Harvard Web Publishing
cilefen
damienmckenna volunteering
dokumori volunteering
greggles organization(s): Colorado Governor's Office of Information Technology - Colorado Digital Service
poker10 organization(s): ActivIT s.r.o.
neclimdul organization(s): APQC
xjm organization(s): Zoocha, xjm
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.