Contribution records
Contributors

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

Give credit to everyone
karens karens
iam_himanshu iam_himanshu
cgillogly cgillogly
michelle Michelle
cronix cronix
basanta86 basanta86
ck9 ck9
mxmilkiib milkmiruku
attilahooper attilahooper
petrelharp petrelharp
Fr0s7 Fr0s7
jgoodwill01 jgoodwill01
ldweeks ldweeks
rismondo rismondo
Skorpjon Skorpjon
jessefulton jessefulton
robbertnl robbertnl
davepoon davepoon
FreddieK FreddieK
jdln jdln
Apfel007 Apfel007
mccrodp mccrodp
gapple gapple
kapep kapep
endiku endiku
merilainen mErilainen
alfthecat AlfTheCat
haggins haggins
baff baff
mickc MickC
selwynpolit selwynpolit
stevebart9 stevebart9
cartagena cartagena
revelstokesnowboard revelstokesnowboard
damienmckenna damienmckenna organization(s): Current
Parkes Design ParkesDesign
marcin-mark marcin-mark
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.