Skip to content

Clarify canonical Git remote URL identity #5685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Yuchao Yan (msyyc) merged 1 commit into from
Oct 14, 2026
Merged

Clarify canonical Git remote URL identity #5685

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .github/skills/do-linter-development-task-one-by-one/app-session-execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,14 @@ publication binding in durable session artifacts:
completion channel; for reviews, selected owner and persistent capabilities

Resolve repository identity from actual remote fetch/push URLs and GitHub
metadata, never a remote's name. New development, migration and promotion heads,
metadata, never a remote's name. Compare the resolved owner/repository, not a
guessed exact URL spelling: `https://github.com/Azure/typespec-azure` and
`https://github.com/Azure/typespec-azure.git` identify the same repository. The
optional `.git` suffix is not a publication or permission gate. Still record the
actual effective push URL/refspec and verify GitHub repository identity and push
permission; URL equivalence alone does not establish the publication binding.

New development, migration and promotion heads,
and all skill-update PR heads, must live in canonical
`Azure/typespec-azure`, not a personal fork. An Azure base repository alone does
not satisfy this requirement. Verify push permission for the authorized head
Expand Down