Issue
Contribution records
Contributors

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

Give credit to everyone
senscybersecurity
cilefen
poker10 organization(s): ActivIT s.r.o.
cmlara organization(s): DM13 Security LLC
spokje volunteering customer(s): Millor
greggles organization(s): HeroDevs
quietone organization(s): PreviousNext
catch organization(s): Third and Grove
smustgrave organization(s): Mobomo
ericgsmith organization(s): Catalyst IT
naveenvalecha organization(s): Morpht customer(s): Morpht
sikofitt volunteering
harpade volunteering
jurgenhaas organization(s): LakeDrops
loopy1492
jamesoakley volunteering
longwave organization(s): Full Fat Things
alexpott organization(s): Acro Commerce, Thunder
xjm organization(s): HeroDevs, Salsa Digital, xjm, Zoocha
dercheffe
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
solideogloria
ram4nd organization(s): Tag1 Consulting, Inc.
dino.amino volunteering
o'briat customer(s): E.voyageurs Technologies
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.