Skip to content
This repository has been archived by the owner on Apr 14, 2024. It is now read-only.

Latest commit

 

History

History
49 lines (31 loc) · 2.18 KB

README.md

File metadata and controls

49 lines (31 loc) · 2.18 KB
Raw

Oselvar GitHub Metrics

The data directory contains Oselvar CSV for the GitHub repositories listed in repositories.txt.

The CSV files are updates hourly by a GitHub Action.

View charts for this data at oselvar.com

Publish your own Oselvar Metrics

You can publish metrics for repositories in you own GitHub organisation and view them on https://oselvar.com/ To do this you need to set up a fork of this repository to host your data.

  1. Click the green Use this template button or follow this link.
  2. Modify repositories.txt and list your GitHub organisation's repositories. If you want to override the default stages in the generated CSV, you can add a ; after the repo name, followed by a comma-separated list of stages.
  3. Commit and push your changes.
  4. Go to oselvar.com to see your data.

See Oselvar Connector for more details, or print the help:

npx @oselvar/connector-github@latest --help

Using a personal GitHub token

The GITHUB_TOKEN provided by GitHub Actions is used by default to extract data from GitHub issues. There are some situations where you may want to use a PERSONAL_GITHUB_TOKEN instead:

  • If you want to extract data from GitHub issues in a different organisation.
  • If your GitHub Action job fails with an error message like GraphqlError: Resource not accessible by integration.

Follow these steps:

  1. Create a new personal access token with public_repo scope. Copy it to your clipboard.
  2. Store your new token in a new PERSONAL_GITHUB_TOKEN repository secret via Settings -> Secrets -> New repository secret.

The next time your GitHub Action runs, it will pick up PERSONAL_GITHUB_TOKEN instead of GITHUB_TOKEN.