Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Test "Update Stack"

Aperta
  • Qualcosa non va?
#9,046 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
git, github, typescript, vscode
Ambito
devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

testplan-item

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:
    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.
Lingua principale
TypeScript
Stelle
2.6k
Fork
800
Merge medio
1g 23h
PR unite (30g)
42

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/vscode-pull-request-github

Tutte le issue di microsoft/vscode-pull-request-github

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.