OpenRailAssociation / OpenRailAssociation/github-org-manager
Consider informing about repositories without connected team
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 14
- Forks
- 6
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 8
Description
A repository for which no team has permission could be a rotten apple.
However, this should not be valid for archived repositories.
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
The issue names no files, tests, or entry points. Start by locating the repository permission and team-association checks, then inspect how archived repositories are represented and excluded. Done means the manager identifies repositories with no connected team, informs users about them, and does not report archived repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100