Skip to content
Merged
Changes from all commits
Commits
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
10 changes: 6 additions & 4 deletions .github/workflows/extension-template-sync.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,8 +65,8 @@ Key **mypy-specific areas** that are NOT expected to match the template:

### Step 1: Fetch recent template PRs

- List the last 50 merged PRs in `microsoft/vscode-python-tools-extension-template`.
- If there are no merged PRs, stop.
- List merged PRs in `microsoft/vscode-python-tools-extension-template` that were merged in the **last 48 hours**. Ignore any PRs merged before that window.
- If there are no recently merged PRs, stop.

### Step 2: For each merged PR, detect missing changes

Expand Down Expand Up @@ -96,7 +96,7 @@ For each unsynced template PR, use the `create-issue` safe output with:
Changes from the upstream [vscode-python-tools-extension-template](https://github.com/microsoft/vscode-python-tools-extension-template) have not yet been incorporated into this repository.

#### Source PR
- microsoft/vscode-python-tools-extension-template#<NUMBER> — <title>
- [microsoft/vscode-python-tools-extension-template#<NUMBER> — <title>](https://github.com/microsoft/vscode-python-tools-extension-template/pull/<NUMBER>)

#### Summary
<Brief summary of what the template PR changed and why.>
Expand All @@ -114,10 +114,12 @@ Changes from the upstream [vscode-python-tools-extension-template](https://githu
🤖 This issue was auto-generated by the [`extension-template-sync`](.github/workflows/extension-template-sync.md) workflow.
```

**IMPORTANT**: When referencing a template PR anywhere in the issue (title, body, or comments), always use the **full URL** (e.g., `https://github.com/microsoft/vscode-python-tools-extension-template/pull/123`), never the shorthand `#123` or `microsoft/vscode-python-tools-extension-template#123`, to avoid confusion with this repository's own issues and PRs.

### Step 4: Handle edge cases

- **CI/workflow files** (`.github/workflows/`, Azure Pipelines): These are often shared — still assess relevance.
- **Large refactors**: Flag differing files and summarize in the issue body.
- **Dependency updates** (`requirements.in`, `requirements.txt`, `package.json`): Only consider shared dependencies, not tool-specific ones.
- **No unsynced changes found**: Do nothing — do not create any issues.
- **Already-open issues**: Before creating a new issue, search for existing open issues in this repository with the same title pattern (`Template Sync: <title>`). If one already exists for the same template PR, skip it to avoid duplicates.
- **Duplicate prevention**: Before creating a new issue, search for existing issues **and** pull requests in this repository — both **open and closed** — with the same title pattern (`Template Sync: <title>`) or that reference the same template PR number. If a matching issue or PR already exists, skip it to avoid duplicates.
Loading