otto-de / otto-de/gitactionboard
Monitor all / filter repositories in organization
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 159
- Forks
- 38
- Avg merge
- 2m
- Merged PRs (30d)
- 10
Description
Is your feature request related to a problem? Please describe.
The dashboard is very handy for monitoring workflow success and failures however the specification of repositories can become quite unruly if an organization has many repositories.
Describe the solution you'd like
Provide the ability to monitor all repositories or allow wildcard matching.
Example: I may have a template repository and client repositories are created from this template with the same naming convention such as:
Test-Repo-Client-A
Test-Repo-Client-B
docker run \
-p <host machine port>:8080 \
-e REPO_OWNER_NAME=<organization/username> \
-e REPO_NAMES="Test-Repo-Client*" \
-it ottoopensource/gitactionboard:<docker tag>
Example: Monitor all current and future repositories within an organization:
docker run \
-p <host machine port>:8080 \
-e REPO_OWNER_NAME=<organization/username> \
-e REPO_NAMES="*" \
-it ottoopensource/gitactionboard:<docker tag>
This helps in case there are other contributors creating repositories at random which requires constant updating of the environment variables.
Describe alternatives you've considered
None that I can think of
Additional context
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the REPO_OWNER_NAME and REPO_NAMES environment variables are read and how repositories are selected for monitoring. Define the behavior for wildcard patterns and for "*", including repositories created later, then verify that the dashboard discovers and monitors the matching repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, java
- Domain
- devops, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100