Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Test "Update Stack"

Ouverte
  • Quelque chose ne va pas ?
#9,046 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
30/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
Active
Stack technique
git, github, typescript, vscode
Domaine
devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
TypeScript
Étoiles
2.6k
Forks
805
Merge moyen
2 j 3 h
PR mergées (30 j)
38

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/vscode-pull-request-github

Toutes les issues de microsoft/vscode-pull-request-github

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.