Contribution records
Contributors

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

Give credit to everyone
effulgentsia effulgentsia
plach plach volunteering
fago fago
benjy benjy organization(s): Unearthed
tacituseu tacituseu
timmillwood timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
amateescu amateescu customer(s): Pfizer, Inc.
joelpittet joelpittet organization(s): The University of British Columbia
andypost andypost volunteering organization(s): Skilld
jofitz jofitz organization(s): ComputerMinds
sam152 sam volunteering organization(s): PreviousNext
jibran jibran volunteering
johnwebdev johnwebdev
catch catch organization(s): Third and Grove
yched yched
skaught SKAUGHT volunteering
larowlan larowlan organization(s): PreviousNext
mondrake mondrake volunteering
dillix dillix
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.