Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add issue templates#1410

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.

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

Already on GitHub?Sign in to your account

Merged
andrewbranch merged 3 commits intomainfromandrewbranch-patch-1
Jul 17, 2025
Merged

Add issue templates#1410

andrewbranch merged 3 commits intomainfromandrewbranch-patch-1
Jul 17, 2025

Conversation

andrewbranch
Copy link
Member

No description provided.

@CopilotCopilotAI review requested due to automatic review settingsJuly 16, 2025 18:32
Copy link
Contributor

@CopilotCopilotAI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Pull Request Overview

This PR adds GitHub issue templates to help standardize issue reporting and facilitate specific workflows for the TypeScript-to-Go port project. The templates provide structured forms for different types of issues and automated workflows.

  • Adds templates for crash reports, behavior differences, and general issues
  • Creates a specialized template for Copilot to port PRs from microsoft/TypeScript
  • Establishes consistent labeling and assignment patterns for issue management

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

FileDescription
.github/ISSUE_TEMPLATE/crash.mdTemplate for crash reports with stack trace and reproduction steps
.github/ISSUE_TEMPLATE/behavior-difference.mdTemplate for reporting differences between tsgo and TypeScript 5.8 behavior
.github/ISSUE_TEMPLATE/copilot-pr-porting.mdSpecialized template with instructions for Copilot to port PRs from upstream
.github/ISSUE_TEMPLATE/other.mdGeneric template for miscellaneous issues

@andrewbranchandrewbranch marked this pull request as draftJuly 16, 2025 18:32
@andrewbranchandrewbranch marked this pull request as ready for reviewJuly 16, 2025 18:37
@@ -0,0 +1,16 @@
---
name:Behavior Difference
about:tsgo produces different results than TypeScript 5.8

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Suggested change
about: tsgo produces different results than TypeScript 5.8
about: tsgo produces different results than TypeScript 5.x
Suggested change
about: tsgo produces different results than TypeScript 5.8
about: tsgo produces different results than TypeScript 5.8+


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

##Behavior with`typescript@5.8`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Suggested change
##Behavior with`typescript@5.8`
##Behavior with`typescript@5.x`

Not sure if specifically calling out5.8 was intentional

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It was, since using a too-new or too-old version could explain the behavior difference.

- 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.

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

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.

Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>
@andrewbranchandrewbranch added this pull request to themerge queueJul 17, 2025
Merged via the queue intomain with commitd0520d8Jul 17, 2025
22 checks passed
@andrewbranchandrewbranch deleted the andrewbranch-patch-1 branchJuly 17, 2025 16:22
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

Copilot code reviewCopilotCopilot left review comments

@DanielRosenwasserDanielRosenwasserDanielRosenwasser approved these changes

@RyanCavanaughRyanCavanaughRyanCavanaugh approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@andrewbranch@DanielRosenwasser@RyanCavanaugh

[8]ページ先頭

©2009-2025 Movatter.jp