Permalinks in feature branches on forks should fallback to upstream main for unmodified lines
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 30/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Stack tecnologico
- github, typescript, vscode
- Ambito
- developer-experience, devtools
Direzione di ricerca
Inizia controllando la logica relativa ai permalink e l’esempio build/filters.js menzionato nell’issue, poi individua i test che coprono i link ai fork e ai feature branch. Definisci la precedenza tra i branch upstream predefiniti o configurati e verifica che le righe non modificate utilizzino link upstream, mentre le righe modificate mantengano i link al fork; l’issue non indica alcun test esistente né alcun punto di ingresso.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
Referencing prior fix in PR #1816: Permalinks generated from feature branches on forks do not fallback to upstream main, even for lines that are completely unmodified. This harms canonical link-sharing because:
- Links to feature branches break when the branch is deleted (common after PR merge)
- Recipients may not have access to fork repositories
- The same code exists in upstream main but the link doesn't redirect there
Current Behavior
When creating a permalink from a feature branch on a fork:
- The link points to:
fork/repo/blob/feature-branch/file.ext#L123 - No fallback occurs even if line 123 is identical in upstream
main - Link becomes invalid after branch deletion
Proposed Enhancement
Extend the permalink generation logic to:
- Check if the referenced lines exist unchanged in upstream
main - If unchanged, generate permalink to upstream
maininstead - Fall back to checking other long-lived branches if not in
main - Only use feature branch permalink if code is actually modified
main here be substituted for any default branches, or custom list thereof user can config for reference in order of prefernce
ie main/master/release-5/release-4 whereby main is preferred, but if snippet only exists in a release branch, not main, release branch in upstream is still preferred vs fork link, since it affects ability to paste into upstream github and getting content previews.
vs
Context Summary
| Aspect | Current State | Proposed State |
|---|---|---|
| Fork feature branch (unchanged code) | Links to fork/branch | Links to upstream/main |
| Fork feature branch (changed code) | Links to fork/branch | Links to fork/branch |
| After branch deletion | Link breaks | Link still works |
| Accessibility | Fork access required | Public upstream access |
Benefits
- More resilient permalink sharing
- Better canonical link behavior
- Reduced broken links after PR merges
- Improved accessibility for external collaborators
This would make permalinks more useful for documentation, issue references, and knowledge sharing.
related: https://github.com/microsoft/vscode-pull-request-github/issues/1781
- Lingua principale
- TypeScript
- Stelle
- 2.6k
- Fork
- 796
- Merge medio
- 1g 4h
- PR unite (30g)
- 46
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/vscode-pull-request-github
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
Issue 3 — Documentation Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
microsoft/vscode-pull-request-github#8966 · 1 assegnatario ·
-
microsoft/vscode-pull-request-github#8965 · 1 assegnatario ·
-
Unable to convert pull request to draft. Cannot read properties of null (reading 'pullRequest') Aperta
microsoft/vscode-pull-request-github#8961 · 1 assegnatario ·
Tutte le issue di microsoft/vscode-pull-request-github
Issue simili
-
comp/dashboard P3 type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 76/100
-
code-quality refactoring
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
langchain-ai/deepagents#6450 ·