Kernel tree tracking is not aligned with usual semantics of a kernel tree
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
The current implementation of the dashboard matches "trees" by tree_name and git_repository_url, sometimes matching on git_repository_branch as well. However, the decentralized nature of git means that definition is prone to errors on multiple cases (e.g. a git:// URL won't match an https:// URL for the same repo). A system more closely aligned with the semantics of a kernel "tree" would be an improvement.
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 locating the dashboard code that matches trees using tree_name, git_repository_url, and optionally git_repository_branch. Review how those fields are stored and compared, then examine existing tests or data for equivalent repositories expressed with different Git URLs. Done means the matching behavior follows a defined kernel-tree identity rather than relying only on URL spelling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100