This message was deleted.
# feature-requestss
Slackbot
11/17/2023, 7:57 PMThis message was deleted.
m
Michael Slevin
11/17/2023, 7:58 PMAnd yes, the tracked branch/target/base for the 2nd PR in the stack is
maine
Enrico Guiraud
11/17/2023, 11:06 PMYes, the fact that there was a PR number 1 before really loses meaning once it's merged: the parent of 2 is now main and 1 is just one more commit in that parent
Enrico Guiraud
11/19/2023, 10:10 AMmmh however after all of the PRs in the stack have been merged, it's sometimes useful to go back to the PR in graphite and see what stack it belonged to
Enrico Guiraud
11/19/2023, 10:10 AM(the full stack)
p
Pranathi Peri
11/20/2023, 3:54 PMHey guys - thanks for flagging!
I believe we leave merged PRs in this visualization for the reason @Enrico Guiraud mentioned. cc @Jacob Gold for more info
j
Jacob Gold
11/20/2023, 6:17 PMCorrect. We've discussed allowing users to remove branches from the stack manually for this reason, but until we build more functionality here we decided that more information was a better default.