![\"demo\"](\"https://user-images.githubusercontent.com/1911623/52544866-51102b00-2d92-11e9-9d9a-323470c1b0af.gif\")
\n\n![](\"https://opencollective.com/git-history/sponsor/0/avatar.svg\"){kind=avatar}
\n\n### Backers\n\nThank you to all our backers! ๐ [[Become a backer](https://opencollective.com/git-history#backer)]\n\n![](\"https://opencollective.com/git-history/backers.svg?width=890\")
\n"
},
{
"path": "cli/server.js",
"content": "const serve = require(\"koa-static\");\nconst Koa = require(\"koa\");\nconst pather = require(\"path\");\nconst getCommits = require(\"./git\");\nconst getPort = require(\"get-port\");\nconst open = require(\"open\");\nconst router = require(\"koa-router\")();\nconst argv = require(\"yargs\")\n .usage(\"Usage: $0 ![\"demo\"](\"https://user-images.githubusercontent.com/1911623/54575634-9b10b000-49d3-11e9-8a19-56e40636e45d.gif\")
\n\n![\"selefra\"](\"https://github.com/selefra.png\" "\\"Selefra\\"")
\n\n\n\n### Backers\n\nThank you to all our backers! ๐ [[Become a backer](https://opencollective.com/git-history#backer)]\n\n\n\n### Thanks\n\nBrowser testing via ![\"LambdaTest\"](\"https://www.lambdatest.com/resources/images/logo-white.svg\"){kind=logo}
\n
\n Loading {path} history {repo ? \"from \" + repo : \"\"}...\n
\n\n GitHub API rate limit exceeded for your IP (60 requests per hour).\n
\nSign in with GitHub for more:
\nFile not found.
\n {gitProvider.isLoggedIn && !gitProvider.isLoggedIn() && (\nIs it from a private repo? Sign in:
\nUnexpected error. Check the console.
\nAlso available as extensions:
\n\n\n \n );\n}\n\nfunction ResponsivePicture({ link, src, alt, append = \"\" }) {\n return (\n \n{children}
\n \n\n \n {name}\n \n \n
\n Support this project by becoming a sponsor. Your logo will show up\n here with a link to your website.{\" \"}\n \n Become a sponsor\n \n
\n\n Thank you to all our backers!{\" \"}\n \n ๐\n \n .{\" \"}\n \n Become a backer to help us ship more features!\n \n
\n\n Browser testing via{\" \"}\n
\n\n\n\n### Backers\n\nThank you to all our backers! ๐ [[Become a backer](https://opencollective.com/git-history#backer)]\n\n\n"
},
{
"path": "vscode-ext/test/extension.test.js",
"content": "/* global suite, test */\n\n//\n// Note: This example test is leveraging the Mocha test framework.\n// Please refer to their documentation on https://mochajs.org/ for help.\n//\n\n// The module 'assert' provides assertion methods from node\nconst assert = require(\"assert\");\n\n// You can import and use all API from the 'vscode' module\n// as well as import your extension to test it\n// const vscode = require('vscode');\n// const myExtension = require('../extension');\n\n// Defines a Mocha test suite to group tests of similar kind together\nsuite(\"Extension Tests\", function() {\n // Defines a Mocha unit test\n test(\"Something 1\", function() {\n assert.equal(-1, [1, 2, 3].indexOf(5));\n assert.equal(-1, [1, 2, 3].indexOf(0));\n });\n});\n"
},
{
"path": "vscode-ext/test/index.js",
"content": "//\n// PLEASE DO NOT MODIFY / DELETE UNLESS YOU KNOW WHAT YOU ARE DOING\n//\n// This file is providing the test runner to use when running extension tests.\n// By default the test runner in use is Mocha based.\n//\n// You can provide your own test runner if you want to override it by exporting\n// a function run(testRoot: string, clb: (error:Error) => void) that the extension\n// host can call to run the tests. The test runner is expected to use console.log\n// to report the results back to the caller. When the tests are finished, return\n// a possible error to the callback or null if none.\n\nconst testRunner = require(\"vscode/lib/testrunner\");\n\n// You can directly control Mocha options by configuring the test runner below\n// See https://github.com/mochajs/mocha/wiki/Using-mocha-programmatically#set-options\n// for more info\ntestRunner.configure({\n ui: \"tdd\", // the TDD UI is being used in extension.test.js (suite, test, etc.)\n useColors: true // colored output from test results\n});\n\nmodule.exports = testRunner;\n"
},
{
"path": "vscode-ext/test-git.js",
"content": "#!/usr/bin/env node\n\n// node test-git.js extension.js 2 94c91d9\n\nconst getCommits = require(\"./git\");\n\nconst [, , path, last, before] = process.argv;\n\ngetCommits(path, last, before).then(cs =>\n console.log(\n cs\n .map(c => {\n return `${c.hash} ${c.date.toDateString()} ${c.message}`;\n })\n .join(\"\\n\")\n )\n);\n"
},
{
"path": "vscode-ext/vsc-extension-quickstart.md",
"content": "## What's in the folder\n\n- This folder contains all of the files necessary for your extension.\n- `package.json` - this is the manifest file in which you declare your extension and command.\n - The sample plugin registers a command and defines its title and command name. With this information VS Code can show the command in the command palette. It doesnโt yet need to load the plugin.\n- `extension.js` - this is the main file where you will provide the implementation of your command.\n - The file exports one function, `activate`, which is called the very first time your extension is activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.\n - We pass the function containing the implementation of the command as the second parameter to `registerCommand`.\n\n## Get up and running straight away\n\n- Press `F5` to open a new window with your extension loaded.\n- Run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Git File History`.\n- Set breakpoints in your code inside `extension.js` to debug your extension.\n- Find output from your extension in the debug console.\n\n## Make changes\n\n- You can relaunch the extension from the debug toolbar after changing code in `extension.js`.\n- You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes.\n\n## Explore the API\n\n- You can open the full set of our API when you open the file `node_modules/vscode/vscode.d.ts`.\n\n## Run tests\n\n- Open the debug viewlet (`Ctrl+Shift+D` or `Cmd+Shift+D` on Mac) and from the launch configuration dropdown pick `Extension Tests`.\n- Press `F5` to run the tests in a new window with your extension loaded.\n- See the output of the test result in the debug console.\n- Make changes to `test/extension.test.js` or create new test files inside the `test` folder.\n - By convention, the test runner will only consider files matching the name pattern `**.test.js`.\n - You can create folders inside the `test` folder to structure your tests any way you want.\n"
}
]