Contribution records
Contributors

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

Give credit to everyone
jonnyeom jonnyeom volunteering
shaunjohnston logicalor volunteering organization(s): Stackful customer(s): Brisbane Bushwalkers Club Inc.
dunebl dunebaud
designwork designwork
eric115 Eric115 volunteering organization(s): PreviousNext
larowlan larowlan organization(s): PreviousNext customer(s): Service NSW
sivakarthik229 sivakarthik229 volunteering organization(s): Infosys
paulmckibben paulmckibben organization(s): Turbojet Technologies
shaung75 shaung75
hswong3i hswong3i organization(s): PantaRei Design Limited (Hong Kong)
tobiasb tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen
smustgrave smustgrave organization(s): Mobomo
s@ilor s-at-ilor
mero.s mero.S volunteering organization(s): AnyforSoft customer(s): AnyforSoft
joseph.olstad joseph.olstad
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.