https://github.com/robandpdx/stale-repo-finder

https://github.com/robandpdx/stale-repo-finder

Last synced: about 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/robandpdx/stale-repo-finder
• Owner: robandpdx
• License: mit
• Created: 2022-04-04T16:29:16.000Z (almost 3 years ago)
• Default Branch: main
• Last Pushed: 2024-06-26T17:44:47.000Z (7 months ago)
• Last Synced: 2024-11-04T11:11:55.590Z (2 months ago)
• Language: Dockerfile
• Size: 230 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# stale-repo-finder

This repo contains the following actions workflow.

1. A workflow that will identify “stale” repos in an org or list of orgs. This workflow will take as input

    1. A list of orgs, comma separated.

    2. A number of days for considering if a repo is stale.

    3. A minimum repo size in megabytes. Only repos larger than this size will be considered.

    The workflow will create a csv file for each org with the following fields:

    1. Repo name

    2. Number of days since last activity

    3. Repo size

    5. List of contributors

    The csv file(s) will be checked into source control in the same repo as the workflow.

You will need to add a secret called `TOKEN` to this repo. The value needs to be a PAT that has access to the orgs you are looking in.

## Debugging locally

Unit tests are contained in [.github/scripts/test.js](.github/scripts/test.js). In VSCode, you can run the  `Mocha` launch config from the debug interface to hit breakpoints and step through code.