Issue
Contribution records
Contributors

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

Give credit to everyone
RemyAroundTown
glynster
matthiasm11 organization(s): MM-Experience
oadaeh organization(s): Hook 42 customer(s): Zicasso, Inc.
johnzzon organization(s): Kodamera AB
robertgarrigos
damienmckenna organization(s): Current
alesr
joelpittet organization(s): The University of British Columbia
majdi volunteering
szeidler organization(s): Ramsalt Lab
ikeigenwijs
plazik volunteering
dchatry volunteering
novitsh volunteering organization(s): Dazzle
nancydru
nanobyt3 volunteering
rjensen
tomarnold2 volunteering
botris
magoomby2
artem0793 organization(s): Adyax
azovsky
krak
cobenash
alysaselby
mdolnik volunteering
malcolm_p
adamevertsson volunteering
FireHawkX
goodmuyis volunteering
solideogloria
oranges13
liam morland organization(s): University of Waterloo
fox mulder
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.