Contribution records
Draft
Contributors

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

Give credit to everyone
iancawthorne iancawthorne
sokru kallevu
catch catch organization(s): Third and Grove
quietone quietone organization(s): PreviousNext
ivnish ivnish volunteering
marcushenningsen marcushenningsen
michaelvanh michaelvanh
mortona2k mortona2k
ishani patel IshaniPatel
paul mosincat paul_mosincat
mhasan14 mhasan14
mradcliffe mradcliffe volunteering organization(s): Kosada
bluedman70 bluedman70
kkho01 kkho01 volunteering
iprince iprince volunteering
rkoller rkoller
bernardm28 bernardm28
n1k n1k
atropoides Atropoides organization(s): erdfisch customer(s): German Aerospace Center
bluegeek9 bluegeek9 volunteering organization(s): Knowledge Learning Labs, Portland Webworks
gorkagr gorkagr organization(s): Erasmus Student Network
jon pugh jonpugh
kentr kentr volunteering
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.