Test "Update Stack"
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 30/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- git, github, typescript, vscode
- 领域
- devtools
调研方向
This is a manual QA checklist, not a code change, and the payload names no source files or tests. Set up a repo with a three-PR stack and a pre-release build of the extension, then work through the three scenarios: partially out of date stack, stack behind its base branch, and no branch checked out. Done means each checkbox is verified on macOS, Linux and Windows, with any failures reported on the issue.
由索引模型根据 Issue 内容生成。
描述
Refs: https://github.com/microsoft/vscode-pull-request-github/pull/9013
- macOS
- linux
- windows
Complexity: 4
Setup
- Install the latest pre-release of GitHub Pull Requests
- Open a clone of a GitHub repo
- You will also need at least one stack of PRs. If you don't have one, here's how to create one:
- Create a PR
- From the head branch of the PR, create a new branch, make a change, and commit.
- With the extension, create a new PR from this branch, with the base branch being the head of the previous PR
- Verify that you see an option to create a stack
- Create the PR and verify that the PRs are stacked
Note
- Resolving merge conflicts is not yet supported. If there are merge conflicts, "Update Stack" will not be offered.
Test a partially out of date stack
- Have a stack of at least 3 PRs
- Make a change in the middle PR
- Make sure you have one of the PRs in the stack checked out.
- Open all of the PR webviews in the stack. Verify that they all offer "Update Stack" in the stack section.
- Use "Update Stack". Verify that the top PR in the stack is rebased and the results are pushed to GitHub.
Test a stack that is out of date with the base branch
- Have a stack of at least 2 PRs
- Make a change on the base branch (the branch that the bottom PR of the stack wants to merge into). Do not introduce a merge conflict.
- Make sure you have one of the PRs in the stack checked out.
- Open all of the PR webviews in the stack. Verify that they all offer "Update Stack" in the stack section.
- Use "Update Stack". Verify all the PRs in the stack are rebased in a cascading rebase and are afterwards up-to-date with the base branch.
Test that "Update Stack" isn't offered when branch isn't checked out
- Open the PR webview of a PR that's part of a stack.
- Make sure that none of the branches in the stack are checked out.
- Verify that "Update Stack" isn't offered.
- 主要语言
- TypeScript
- 星标
- 2.6k
- 派生
- 805
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 42
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/vscode-pull-request-github 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
microsoft/vscode-pull-request-github#8792 ·
维护者通常 1 天内回复
-
PR description view doesn't show PR events可能已有人在做 @alexr00 于 1 天前认领。 未关闭
microsoft/vscode-pull-request-github#9051 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Issue links in overview HTML are emitted with an extra quote in href可能已有人在做 @alexr00 于 4 天前认领。 未关闭bug
microsoft/vscode-pull-request-github#9022 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Colours are off for sub-buttons under Create Merge Commit可能已有人在做 @alexr00 于 5 天前认领。 未关闭info-needed
microsoft/vscode-pull-request-github#9019 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Run: Use multiple accounts per host, including GitHub.com可能已有人在做 @TylerLeonhardt 于 9 天前认领。 未关闭authentication feature-request GitHubEnterprise
microsoft/vscode-pull-request-github#9005 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 microsoft/vscode-pull-request-github 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
NousResearch/hermes-agent#136483 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复
-
factory-active factory-automatic task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
[Bug]: Web chat input doesn't regain focus after a reply finishes可能已有人在做 @GaijinSystems 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
zeroclaw-labs/zeroclaw#11658 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
babylonlabs-io/babylon-toolkit#2711 ·
维护者通常 1 天内回复