Issue
Contribution records
Contributors

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

Give credit to everyone
paulmckibben organization(s): Turbojet Technologies customer(s): Current
sonnykt organization(s): Salsa Digital
gg4
jasonawant organization(s): Nerdery
platinum1
marfillaster volunteering
dorficus organization(s): Nerdery customer(s): Nestle Purina PetCare - United States
bbombachini organization(s): Northern Commerce
douggreen
azinck organization(s): Forum One
joshua1234511 volunteering organization(s): Salsa Digital customer(s): Salsa Digital
ameymudras organization(s): Salsa Digital
alexgreyhead
seanb
juanolalla organization(s): Peak Digital, LLC
joseph.olstad
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
g-brodiei volunteering
martijn de wit organization(s): Ablerz
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.