Contribution records
Contributors

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

Give credit to everyone
thelocaltourist thelocaltourist
sirnjeet sirnjeet
rollingnet rollingnet
kamenrs kamenrs
daemonchrist daemonic
blasthaus blasthaus
flocondetoile flocondetoile
emmonsaz emmonsaz
sch2 sch2
m4olivei m4olivei volunteering
bdupls dupls
retiredpro retiredpro
mxt MXT
pedronau pedronau volunteering
colan colan organization(s): Colan Schwartz Consulting customer(s): Chapter Three (acquired by Kanopi Studios)
jamesrward jamesrward volunteering
broeker broeker
kingdutch Kingdutch organization(s): Ontdekbier
chrisfromredfin chrisfromredfin
ckoharj ckoharj
chegor chegor organization(s): OAO Solution Spark
pmoz pmoz
damienmckenna damienmckenna organization(s): Current
riddhi.addweb Jigar.tanna organization(s): AddWeb Solution Pvt. Ltd.
Berliner-dupe Berliner-dupe
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.