otto-de / otto-de/gitactionboard
Allow Multiple REPO_OWNER's in single instance
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.
Yes and no, we have private repositories split across several different restriction levels maintained under different REPO_OWNER_NAME values. Right now there's no way to monitor across multiple organizations in a single instance.
Describe the solution you'd like
A possible solution would be to allow/force users to specify the full repo name as the REPO_NAME. So REPO_OWNER_NAME/REPO_NAME instead of splitting it into two vars.
Describe alternatives you've considered
NA
Additional context
NA
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 REPO_OWNER_NAME and REPO_NAME are read and passed into repository monitoring. Define the configuration shape for repositories across multiple owners, then verify that one instance can monitor each specified repository without breaking existing single-owner configuration. The issue mentions no files or tests, so locate the relevant configuration and monitoring entry points first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100