branch uniqueness doesn't consider namespaces
Open
Nobody has claimed this yet.
actor/kelos
kelos/needs-input
kind/bug
priority/important-longterm
triage-accepted
- Dominant language
- Go
- Stars
- 331
- Forks
- 40
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 70
Description
There should be a Task for a name for a specific workspace (which is a namespaced resource).
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 Task names and branch uniqueness are validated, then inspect how workspace namespaces are represented in the Kubernetes-related code. Determine which existing tests cover duplicate names or branches. Done means uniqueness is evaluated within the relevant workspace namespace, with tests demonstrating the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100