NodeGit seems to treat Git submodules as regular files. When our tool iterates through test files in a commit and comes across a submodule, it breaks. Fix it so that the tool will gracefully exclude submodules when counting lines of code.

Start with

Is the issues a pull request? If not, continue (allow this step to be flagged off)
Does the issue have a user-specified (CLI) label? If yes, count the issue
Does the issue have a user-specified label in the title or body? If yes count the issue, else skip it

https://github.com/ansible/ansible
https://github.com/sampsyo/beets

Currently we measure unit test volume solely by counting the lines in all test files. We have received comments that measuring the ratio of unit tests to the entire project size may return more accurate results.

What would be the best way to get this ratio and are there any other more accurate ways to measure unit test volume?

Now that the project is a bit more mature and we have 4 developers contributing, it would be good to start using pull requests so that everyone can get some eyes on the code and know what's going on.

Wrap current functionality in issues.js into a class so that we can write a main program that uses it to fetch all the issues into a nice array.

also gives NaN in derivative:

Currently we have the pattern variable as described below, we just need to implement a check before we assign the console inputs.

    var usernameConfig = {
        name: "username",
        description: "GitHub Username",
        pattern: /^[a-zA-Z\s\-]+$/,
        message: "Username must be only letters, spaces, or dashes"

I can work on this in my FilterIssues branch as I am already working on adding more console options. Any idea which module has the check against regex feature @jordan-heemskerk ?

Is the tool working properly?

QA steps.

Cache issues so that we don't need to grab them everytime

Modify server.js to accept a port number as a command line argument. This will be the port the web server listens to. Perhaps make a default port (ie. 80) if no port was specified.

https://developer.github.com/v3/auth/

Gift doesn't give any ability to search by date, so we should use a more powerful tool.

See https://github.com/nodegit/nodegit

Right now the line number count only looks for files within the immediate root of the test directory. Change this to also look for files in every subdirectory within the test directory recursively.

Right now we have a fatal error when the headers can't be parsed because they aren't what we expect. We need to check the status code of the response

i cloned our repo on a new laptop and did the npm install as instructed but it gave me this error when i run the code.

bash-4.2$ node src/main.js
module.js:338
    throw err;
          ^
Error: Cannot find module 'nodegit-promise'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/rsaujla/seng371/SoftwareEvolutionAnalysis/node_modules/nodegit/lib/nodegit.js:1:77)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)

Add a command line argument for a filter applied to test files to only count lines on files that match the expression.

They come in as JSON, so we should just be able to keep them in main memory as an array of objs

Guys, it would be good if we had a proper name for what were building

Maybe we can async does this in parallel with getting all the issues

Not sure if we want to automatically pull new changes, throw a fatal error, clear the repo_cache, etc.

https://plot.ly/nodejs/

I ran AngularJS and Mozilla-firefox repositories thought node. it only showed zero lines of code in the commit history. I did input there test folder in Unit test directory. I am not sure if its a bug or if i am not running it correctly.

Right now there is no way for the user to view the graphs produced by Plotly. Have the tool output an HTML document that will contain an iFrame pointing to the generated Plotly graph.

If possible, try to have the HTML document open automatically.

At the moment we just pull all GitHub issues for the project. We need to discuss how we plan to filter the issues to better represent bugs - whether its by label (ie. "bug"), keywords, etc.

Do we want to use the same criteria for all, or allow the user to specify the criteria? Allowing the user the specify the criteria may produce better results since they can do it on a case by case basis.