Contribution records
Contributors

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

Give credit to everyone
LindenLion LindenLion
catch catch
karens karens
yched yched
metaface metaface
danielb danielb
brianV brianV
buckley buckley
jwuk jwuk
webchick webchick
sivaji_ganesh_jojodae sivaji
jhedstrom jhedstrom
David_Rothstein drothstein
JacobSingh JacobSingh
mikeytown2 mikeytown2
kscheirer kscheirer
tizzo tizzo
sumitk sumit
nicolash nicolash
halstead halstead
kr0k kr0k
chx chx
yannickoo yannickoo
kristiaanvandeneynde kristiaanvandeneynde
disasm disasm
aspilicious aspilicious
djdevin devin
marcingy marcingy
xjm xjm
no_commit_credit no_commit_credit
kid_icarus kid_icarus
yesct YesCT
dcam dcam
fengtan Fengtan
royal121 royal121
pwolanin pwolanin
hgoto gh640 volunteering
parashram Parashram organization(s): ]init[ AG
pol Pol organization(s): European Commission and European Union Institutions, Agencies and Bodies customer(s): European Commission and European Union Institutions, Agencies and Bodies
moshe weitzman weitzman
gábor hojtsy goba
jody lynn lynn
tim.plunkett tim.plunkett
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.