Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Test "Update Stack"

Abierto
  • ¿Algo no está bien?
#9,046 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git, github, typescript, vscode
Área
devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
2.6k
Forks
800
Merge medio
1 d 23 h
PR fusionados (30 d)
42

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/vscode-pull-request-github

Todos los issues de microsoft/vscode-pull-request-github

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.