Contribution records
Contributors

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

Give credit to everyone
guncha25 guncha25
cilefen cilefen
larowlan larowlan organization(s): PreviousNext
znerol znerol
dawehner dereine volunteering
kenorb kenorb
moonray moonray organization(s): Chapter Three (acquired by Kanopi Studios)
vprocessor vprocessor organization(s): Skilld
matzab matzAB
andypost andypost volunteering organization(s): Skilld
benjifisher benjifisher organization(s): Isovera
jofitz jofitz organization(s): ComputerMinds
alexpott alexpott volunteering
dinesh18 Dinesh18 volunteering
anya_m anya_m volunteering organization(s): Skilld
opensense vidhatanand organization(s): OpenSense Labs
James Nesbitt JamesNesbitt organization(s): Mearra (formerly known as Wunder)
pritishkumar pritish.kumar organization(s): OpenSense Labs
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.