knative-extensions / knative-extensions/knobots
Auto fork action doesn't cooperate with renamed repositories
Open
- Dominant language
- Shell
- Stars
- 8
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Title. For instance, it still forks `net-gateway-api` as `net-ingressv2` which gives us trouble in subsequent actions (i.e. dep updates)
Contributor guide
Research direction
Start by locating the auto fork action in the knobots repository and trace how it handles renamed repositories. Reproduce the `net-gateway-api` to `net-ingressv2` case, then verify that the fork uses the renamed repository correctly and does not break subsequent dependency updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100