https://github.com/bmartinson/repo-hero

Configurable product management analysis tool for analyzing the health of git repositories and their contributors.
https://github.com/bmartinson/repo-hero

cli git github jira kpi nodejs ranker

Last synced: 5 months ago
JSON representation

Configurable product management analysis tool for analyzing the health of git repositories and their contributors.

• Host: GitHub
• URL: https://github.com/bmartinson/repo-hero
• Owner: bmartinson
• License: mit
• Created: 2024-08-19T04:08:31.000Z (almost 2 years ago)
• Default Branch: master
• Last Pushed: 2026-01-16T01:33:52.000Z (6 months ago)
• Last Synced: 2026-01-16T12:23:18.081Z (6 months ago)
• Topics: cli, git, github, jira, kpi, nodejs, ranker
• Language: JavaScript
• Homepage:
• Size: 214 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# repo-hero

A configurable product management analysis toolkit for analyzing the health of git repositories and their contributors. You may consider this project in an **alpha** state. It is actively being developed in accordance with real world needs. Contributions are welcome.

## Application Configuration

A CLI-based configuration wizard will be included as part of the package in the future to help you build your application config. This configuration is stored at the same directory level as `gather-and-rank.js` and is named `config.json`. Here is an example of a usable application configuration:

_All top level properties are required, except for `aliases`, `ignoreUsers`, `commitsPerPullRequest`, `resultsName`_

```javascript

{

  "tokens": {

    "github": "ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxx" // use a personal access token for GitHub API access

  },

  "directory": "/Users/bmartinson/Development", // where to look for .git projects

  "startDate": "2023-09-01", // the starting range for analysis

  "endDate": "2024-09-01", // the ending range for analysis

  "resultsName": "2024-09", // the name of the results json file, this is optional

  "commitsPerPullRequest": 12.5, // if your projects don't use pull requests and rely mostly on commits, use this to synthesize deliverables (pseudo-PRs)

  "projects": [

    "@bmartinson/repo-hero" // these are all of the project including owner name owner/repo - @ handles should be included

  ],

  "aliases": {

    "User A": [ // the resulting name for a user we care about

      "user-a", // a known alias that we want to turn into "User A"

      "usera"

    ],

    "Brian Martinson": [

      "bmartinson",

      "bmartinson13",

    ]

  },

  "ignoreUsers": [

    "DevOps" // user names that we will remove from the results output

  ]

}

```

## Running The Application

These tools are a work in progress. You can expect a more single run e2e tool that will generate webpages and utilize chart.js, etc. in order to visualize your data gathering. For now, use these various steps to aggregate data.

```sh

### EDIT config.json ###

# Quickly re-configure your config.json to focus on a year

npm run config 2024

# Or quickly do the same to focus on a given YYYY-MM.

npm run config 2024-12

### DISCRETE-STEP OPERATION ###

#

# Gather data based on your config.json file. Continually adjust your config

# for new date ranges to gather all of the information you need.

# See

#

npm run gather # repeat for each config.json mod

# now, combine all of your .results_history output

npm run combine

# once combined, generate useful csv files so you may plot and graph

npm run chart

### ALTERNATIVE OPERATION ###

#

# Want to skip the three step process of gather, combine, chart? Just use start

# to clear your workspace of any combined results and chart data and re-generate

# it all with this.

#

npm start

```