Jul 17, 2025 · Jul 16, 2025 · Jul 16, 2025 · Jul 16, 2025 · Jul 16, 2025 · Jul 16, 2025
diff --git a/.github/ISSUE_TEMPLATE/01-crash.md b/.github/ISSUE_TEMPLATE/01-crash.md
 ---
 name:Crash
 about:Using tsgo or the language server caused a panic
 title:''
 labels:Crash
 assignees:''

 ---

 ##Stack trace

 ```
 [paste stack trace here]
 ```

 ##Steps to reproduce

 1.
diff --git a/.github/ISSUE_TEMPLATE/02-behavior-difference.md b/.github/ISSUE_TEMPLATE/02-behavior-difference.md
 ---
 name:Behavior Difference
 about:tsgo produces different results than TypeScript 5.8
 title:''
 labels:''
 assignees:''

 ---

 ##Steps to reproduce

 <!-- Share a repository link or a code sample-->

 ##Behavior with`typescript@5.8`

 ##Behavior with`tsgo`
diff --git a/.github/ISSUE_TEMPLATE/03-other.md b/.github/ISSUE_TEMPLATE/03-other.md
 ---
 name: Other
 about: Something else
 title: ''
 labels: ''
 assignees: ''

 ---


diff --git a/.github/ISSUE_TEMPLATE/04-copilot-pr-porting.md b/.github/ISSUE_TEMPLATE/04-copilot-pr-porting.md
 ---
 name: '[TypeScript Team Use] Copilot PR porting'
 about: Instructions for Copilot to port a PR from microsoft/TypeScript
 title: 'Port TypeScript PR #[NNNNN]'
 labels: Porting PR
 assignees: ''

 ---

 This repository is a port of microsoft/TypeScript from TypeScript to Go. Since the port began, the following pull request was applied to microsoft/TypeScript. An equivalent change now needs to be applied here.

 ## PR to port

 - PR link: <!-- https://github.com/microsoft/TypeScript/pull/NNNNN -->
 - Squash commit diff: <!-- Copy the squash commit link and append ".patch", e.g. https://github.com/microsoft/TypeScript/commit/a271797c1a95494e5f7aa8075c01941ad25cad08.patch -->

 ## Instructions

 1. Use `playwright` to view the PR listed above
 2. Apply the edits made in that PR to this codebase, translating them from TypeScript to Go.
   - The change may or may not be applicable. It may have already been ported. Do not make any significant changes outside the scope of the diff. If the change cannot be applied without significant out-of-scope changes, explain why and stop working.
   - Tip: search for functions and identifiers from the diff to find the right location to apply edits. Some files in microsoft/TypeScript have been split into multiple.
   - Tip: some changes have already been ported, like changes to diagnostic message text. Tests do not need to be ported as they are imported from the submodule.
 3. Refer to your copilot_instructions.md for guidance on how to build and test your change. Note the following differences to the typical development workflow:
   - Since you are porting the implementation for a behavior that already has tests in the submodule, you don't need to add new tests. Instead, your change should change existing baselines.
   - If done correctly, you should see removals in `.diff` baselines. These `.diff` removals are your ultimate source of truth: your change is not correct unless diffs are reduced.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,18 @@
		---
		name:Crash
		about:Using tsgo or the language server caused a panic
		title:''
		labels:Crash
		assignees:''

		---

		##Stack trace

		```
		[paste stack trace here]
		```

		##Steps to reproduce

		1.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,10 @@
		---
		name: Other
		about: Something else
		title: ''
		labels: ''
		assignees: ''

		---
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,26 @@
		---
		name: '[TypeScript Team Use] Copilot PR porting'
		about: Instructions for Copilot to port a PR from microsoft/TypeScript
		title: 'Port TypeScript PR #[NNNNN]'
		labels: Porting PR
		assignees: ''

		---

		This repository is a port of microsoft/TypeScript from TypeScript to Go. Since the port began, the following pull request was applied to microsoft/TypeScript. An equivalent change now needs to be applied here.

		## PR to port

		- PR link: <!-- https://github.com/microsoft/TypeScript/pull/NNNNN -->
andrewbranch marked this conversation as resolved. Show resolvedHide resolved
		- Squash commit diff: <!-- Copy the squash commit link and append ".patch", e.g. https://github.com/microsoft/TypeScript/commit/a271797c1a95494e5f7aa8075c01941ad25cad08.patch -->

		## Instructions

		1. Use `playwright` to view the PR listed above
		2. Apply the edits made in that PR to this codebase, translating them from TypeScript to Go.
		- The change may or may not be applicable. It may have already been ported. Do not make any significant changes outside the scope of the diff. If the change cannot be applied without significant out-of-scope changes, explain why and stop working.
		- Tip: search for functions and identifiers from the diff to find the right location to apply edits. Some files in microsoft/TypeScript have been split into multiple.
		- Tip: some changes have already been ported, like changes to diagnostic message text. Tests do not need to be ported as they are imported from the submodule.
		3. Refer to your copilot_instructions.md for guidance on how to build and test your change. Note the following differences to the typical development workflow:
		- Since you are porting the implementation for a behavior that already has tests in the submodule, you don't need to add new tests. Instead, your change should change existing baselines.
		- If done correctly, you should see removals in `.diff` baselines. These `.diff` removals are your ultimate source of truth: your change is not correct unless diffs are reduced.
Copy link Member DanielRosenwasserJul 16, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. Nit: diffs might be introduced or modified if there are new paths that are triggered. So at leastsome diffs should be reduced or eliminated, but I wonder if a model would take this too literally. I'm flexible about trying whatever you think is right here though. Copy link MemberAuthor andrewbranchJul 16, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. My experience has been that it's hard to convince the agent to minimize the diffs.