collect more data

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
github-actions, python
Domain
tooling

Research direction

No implementation files, tests, or entry points are named. Start by locating the existing repository-data collection entry point, then use the listed workflows, tools/copyright, .bazelrc, MODULE.bazel, pre-commit, dependabot.yml, devcontainer, and repository-user relationships as the scope; done means each requested item is collected consistently.

Written by the indexing model from the issue text.

Description

good first issue

We want to collect:

  • are repos using the central on-pr.yml workflow
  • are repos using the central daily.yml workflow
  • are repos using the central docs.yml workflow
  • are repos using the central docs-publish.yml workflow
  • are repos using tools/copyright via pre-commit
  • dependencies between repos, i.e. for any repo a list of "users"
  • do they have xxx in .bazelrc?
  • do they have xxx in MODULE.bazel?
  • what do they have in pre-commit
  • do they have a dependabot.yml
  • do they have a devcontainer
Dominant language
Python
Stars
0
Forks
14
Avg merge
6h 8m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-score/.github

All issues in eclipse-score/.github

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.