Contribution records
Contributors

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

Give credit to everyone
theroyal theroyal
larowlan larowlan organization(s): PreviousNext
berdir berdir organization(s): MD Systems GmbH
eiriksm eiriksm organization(s): Ny Media AS, Violinist
plato1123 plato1123
bdanin bdanin
rshafakian rshafakian
Malkiyahu Malkiyahu
technotim2010 TechnoTim2010 volunteering
abx abx
mstef mikestefff
brulain brulain
vvvi VVVi
ugintl ugintl
hugronaphor hugronaphor volunteering organization(s): Acrosto
geerlingguy geerlingguy organization(s): Midwestern Mac, LLC
cilefen cilefen volunteering
kerolar kerolar volunteering
agileadam agileadam
gregbeat gregbeat
akalata akalata
semisem semisem
mjk73 mjk73 volunteering
chrotto chrotto
goodboy gbtools
laurajeans libraryjeans volunteering
sauqi sauqi
fy1128 fy1128
borwickja borwickja
phl3tch CrackWilding
2dareis2do 2dareis2do
dhirendragrazitti Dhirendra
ggallant ggallant volunteering
rick hood rick02840
enrique.diaz enrique.diaz
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.