https://github.com/conda/issue-tracker

A visualization of the issue count of conda org repositories over time.

https://github.com/conda/issue-tracker

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (12.7%) to scientific vocabulary

Keywords from Contributors

energy-system-model parallel
Last synced: 11 months ago · JSON representation

Repository

A visualization of the issue count of conda org repositories over time.

Basic Info
Statistics
  • Stars: 3
  • Watchers: 6
  • Forks: 7
  • Open Issues: 2
  • Releases: 0
Created over 4 years ago · Last pushed 11 months ago
Metadata Files
Readme Changelog License Code of conduct

README.md

Conda (and friends) Issue Tracker

Website

A visualization of the issue count of conda org repositories over time.

This is designed to be a serverless site with a static frontend.

Using GitHub Actions we query at set intervals for the number of issues open for a given repository. We generate snapshots for 4 kinds of graphs:

  • recent (hourly interval over the past 3 days)
  • month (every 3 hours over the past 31 days)
  • year (every 24 hours over the past 366 days)
  • all-time (every 72 hours since the start of time)

Snapshots displayed with Chart.js.

Inspired by VSCode Issue Tracker by Benjamin Lannon.
Credit also goes to GitHub Corners by Tim Holman.

Contributing

Contributions to issue-tracker are welcome, see below for details on configuring your environment.

Code of Conduct

The conda organization adheres to the NumFOCUS Code of Conduct.

Development Environment

  1. Signup for a GitHub account (if you haven't already) and install Git on your system.
  2. Fork the conda repository to your personal GitHub account by clicking the "Fork" button on conda/issue-tracker and follow GitHub's instructions.
  3. Clone the repo you just forked on GitHub to your local machine. Configure your repo to point to both "upstream" (the main repo) and "origin" (your fork):

```bash # choose the repository location $ PROJECT_ROOT="$HOME/issue-tracker"

# clone the project # replace your-username with your actual GitHub username $ git clone git@github.com:your-username/issue-tracker "$PROJECTROOT" $ cd "$PROJECTROOT"

# set the upstream as the the main repository $ git remote add upstream git@github.com:conda/issue-tracker ```

  1. Create a local development environment and activate that environment

```bash # install conda packages $ conda create -n issue-tracker nodejs python pygithub pyyaml rich $ conda activate issue-tracker

# install nodejs packages (issue-tracker) $ npm install ```

Static Code Analysis

This project is configured with pre-commit to automatically run linting and other static code analysis on every commit. Running these tools prior to the PR/code review process helps in two ways:

  1. it helps you by automating the nitpicky process of identifying and correcting code style/quality issues
  2. it helps us where during code review we can focus on the substance of your contribution

Feel free to read up on everything pre-commit related in their docs but we've included the gist of what you need to get started below:

```bash

install pre-commit hooks for conda

(issue-tracker) $ pre-commit install

manually running pre-commit on current changes

note: by default pre-commit only runs on staged files

(issue-tracker) $ pre-commit run

automatically running pre-commit during commit

(issue-tracker) $ git commit ```

Beware that some of the tools run by pre-commit can potentially modify the code (see black and blacken-docs). If pre-commit detects that any files were modified it will terminate the commit giving you the opportunity to review the code before committing again.

Strictly speaking using pre-commit on your local machine for commits is optional (if you don't install pre-commit you will still be able to commit normally). But once you open a PR to contribue your changes, pre-commit will be automatically run at which point any errors that occur will need to be addressed prior to proceeding.

Generating Historical Snapshots

While the idea is to run GitHub Actions on a regular schedule to generate snapshots of data this only appends new data. To generate the historical data run the provided Python program.

To run history.py you need a GitHub personal access token. This can be conveniently stored in your home directory (at ~/.github_apikey) for repeated use.

bash (issue-tracker) $ python history.py

The raw data generated by history.py will be cached to allow for faster testing and fewer expensive calls to GitHub's API. Ignore the cache via --ignore-cache argument:

bash (issue-tracker) $ python history.py --ignore-cache

Running Locally

To test the site locally run http-server from $PROJECT_ROOT:

bash (issue-tracker) $ http-server

Owner

  • Name: conda
  • Login: conda
  • Kind: organization

conda is system-level, binary package and environment manager running on all major operating systems and platforms.

GitHub Events

Total
  • Issues event: 2
  • Watch event: 1
  • Delete event: 6
  • Issue comment event: 2
  • Push event: 19
  • Pull request review event: 9
  • Pull request event: 30
  • Create event: 6
Last Year
  • Issues event: 2
  • Watch event: 1
  • Delete event: 6
  • Issue comment event: 2
  • Push event: 19
  • Pull request review event: 9
  • Pull request event: 30
  • Create event: 6

Committers

Last synced: over 1 year ago

All Time
  • Total Commits: 4,192
  • Total Committers: 5
  • Avg Commits per committer: 838.4
  • Development Distribution Score (DDS): 0.024
Past Year
  • Commits: 30
  • Committers: 2
  • Avg Commits per committer: 15.0
  • Development Distribution Score (DDS): 0.467
Top Committers
Name Email Commits
kenodegard k****d 4,093
pre-commit-ci[bot] 6****] 55
conda-bot 1****t 41
conda-bot a****t@a****m 2
Benjamin Lannon b****n@l****m 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 11 months ago

All Time
  • Total issues: 1
  • Total pull requests: 13
  • Average time to close issues: N/A
  • Average time to close pull requests: 7 days
  • Total issue authors: 1
  • Total pull request authors: 2
  • Average comments per issue: 0.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 8
  • Bot issues: 0
  • Bot pull requests: 6
Past Year
  • Issues: 1
  • Pull requests: 13
  • Average time to close issues: N/A
  • Average time to close pull requests: 7 days
  • Issue authors: 1
  • Pull request authors: 2
  • Average comments per issue: 0.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 8
  • Bot issues: 0
  • Bot pull requests: 6
Top Authors
Issue Authors
  • travishathaway (1)
  • TheProdigyLeague (1)
  • pre-commit-ci[bot] (1)
Pull Request Authors
  • conda-bot (21)
  • pre-commit-ci[bot] (18)
Top Labels
Issue Labels
type::bug (1) type::feature (1)
Pull Request Labels
cla-signed (28)

Dependencies

package-lock.json npm
  • @actions/core 1.6.0
  • @actions/http-client 1.0.11
  • async 2.6.3
  • basic-auth 2.0.1
  • call-bind 1.0.2
  • colors 1.4.0
  • corser 2.0.1
  • debug 3.2.7
  • eventemitter3 4.0.7
  • follow-redirects 1.14.5
  • function-bind 1.1.1
  • get-intrinsic 1.1.1
  • has 1.0.3
  • has-symbols 1.0.2
  • he 1.2.0
  • html-encoding-sniffer 3.0.0
  • http-proxy 1.18.1
  • http-server 14.0.0
  • iconv-lite 0.6.3
  • lodash 4.17.21
  • luxon 2.1.1
  • mime 1.6.0
  • minimist 1.2.5
  • mkdirp 0.5.5
  • ms 2.1.3
  • node-fetch 2.6.6
  • object-inspect 1.11.0
  • opener 1.5.2
  • portfinder 1.0.28
  • qs 6.10.1
  • requires-port 1.0.0
  • safe-buffer 5.1.2
  • safer-buffer 2.1.2
  • secure-compare 3.0.1
  • side-channel 1.0.4
  • tr46 0.0.3
  • tunnel 0.0.6
  • union 0.5.0
  • url-join 4.0.1
  • webidl-conversions 3.0.1
  • whatwg-encoding 2.0.0
  • whatwg-url 5.0.0
package.json npm
  • @actions/core ^1.6.0
  • http-server ^14.0.0
  • luxon ^2.1.1
  • node-fetch ^2.6.6
.github/workflows/alltime.yml actions
  • actions/checkout v2 composite
  • actions/setup-node v2 composite
  • stefanzweifel/git-auto-commit-action v4 composite
.github/workflows/cla.yml actions
  • conda/actions/check-cla v22.9.0 composite
.github/workflows/issues.yml actions
  • actions-ecosystem/action-add-labels v1.1.0 composite
  • actions-ecosystem/action-remove-labels v1.3.0 composite
.github/workflows/labels.yml actions
  • EndBug/label-sync v2.3.0 composite
  • actions/checkout v3 composite
  • andstor/file-existence-action v1.0.1 composite
.github/workflows/lock.yml actions
  • dessant/lock-threads v2 composite
.github/workflows/month.yml actions
  • actions/checkout v2 composite
  • actions/setup-node v2 composite
  • stefanzweifel/git-auto-commit-action v4 composite
.github/workflows/project.yml actions
  • actions/add-to-project v0.3.0 composite
.github/workflows/recent.yml actions
  • actions/checkout v2 composite
  • actions/setup-node v2 composite
  • stefanzweifel/git-auto-commit-action v4 composite
.github/workflows/stale.yml actions
  • actions/stale v4 composite
  • conda/actions/read-yaml v22.9.0 composite
.github/workflows/year.yml actions
  • actions/checkout v2 composite
  • actions/setup-node v2 composite
  • stefanzweifel/git-auto-commit-action v4 composite