[FEATURE QUESTION] repository rename
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 475
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 178
Description
Problem or use case
Is it already possible to rename a github repository without breaking the link to past and future entire logs ?
Desired behavior
Proposed solution
No response
Alternatives or workarounds
No response
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. First clarify how repository renames should preserve links to past and future Entire logs, then locate the repository identity and log-linking paths; done means documented or tested behavior for renamed repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100