Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Test "Update Stack"

Offen
  • Stimmt etwas nicht?
#9,046 0 Kommentare 0 Reaktionen 2 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@benvillalobos arbeitet bereits daran.

Seit 12.10.2026.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
30/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
git, github, typescript, vscode
Bereich
devtools

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

testplan-item

Refs: https://github.com/microsoft/vscode-pull-request-github/pull/9013

  • macOS @federicobrancasi
  • linux @roblourens
  • windows @benvillalobos

Complexity: 4

Create Issue

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:
    1. Create a PR
    2. From the head branch of the PR, create a new branch, make a change, and commit.
    3. With the extension, create a new PR from this branch, with the base branch being the head of the previous PR
    4. Verify that you see an option to create a stack
    5. 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.
Vorherrschende Sprache
TypeScript
Sterne
2.6k
Forks
805
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
38

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/vscode-pull-request-github

Alle Issues in microsoft/vscode-pull-request-github

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.