https://linen.dev logo
Join Slack
Powered by
This message was deleted.
# how-do-i
s
This message was deleted.
a
Hit S on the PR page
You can press 
?
to see all the shortcuts/actions we have. We also have a 
cmd + K
menu that can be searched
🤯 1
c
Just checked this out, but I’m not sure the web app is working? I’m getting the visual chart in the GH PR comments, but according to the web-app, there is no stack? sad parrot
no-stack-bug.mp4
➕ 1
Just me not understanding Stacking or actual bug?
a
What does your gt ls look like
c
I’ve already merged/killed the branches so that’s the best I got. 🙈
a
Ok weird, so this is the general flow I use. Afaict nothing is too broken on our side, so just validating the flow you used to create these.
Copy code
// Create first branch with some changes
$ gt branch create <parent>
$ echo 'tmp' &> $REPO_DIR/tmp
$ git commit -A -m 'tmp'

// Create second branch with diff changes
$ gt branch create <child>
$ echo 'tmp2' &> $REPO_DIR/tmp
$ git commit -A -m 'tmp2'

// Submit stack
$ gt stack submit
c
Ah, I do the create & commit single line flow the CLI page is recommending:
Copy code
// add some stuff
gt branch create -a -m "feat..." new-branch-name

// add some stuff
gt branch create -a -m "feat..." new-branch-name

// submit
gt stack submit
a
Ok yeah that is equivalent to what i have
And that results in a broken stack view
What is ur github handle
c
caseybaggz
a
Let me look at your logs to see if something is off
🙏 1
Could you try this test flow & submit PRs? Want to see if it works:
Copy code
// Create first branch with some changes
$ gt branch create <parent>
$ echo 'tmp' &> $REPO_DIR/tmp
$ git commit -A -m 'tmp'

// Create second branch with diff changes
$ gt branch create <child>
$ echo 'tmp2' &> $REPO_DIR/tmp
$ git commit -A -m 'tmp2'

// Submit stack
$ gt stack submit
c
Sure. Let me wrap up the one I’m working on. Gimme like 10
a
Sounds good
c
I’ll hit you up tomorrow. My brain is dead so I’m going to head out. Should be able to run that first thing in the morning. 👍
graphite 1
@Aryaman alrighty, done! except I used actual work. PRs will be live for a few moments, but you should still see them in the history when they are closed
Yup, still a no-go on the stack in the web UI. Should be 2 of 2
e
I can confirm this issue. Happening to me as well. • I used Graphite 3 months ago successfully on my Mac M1 • After 3 months, I update and attempt to stack PRs again. • Each PR is created independently, nothing is stacked. This means that from the 2nd PR, nothing will be merged to main unless you do the manual work or sync - restack - submit for each branch
I believe this is also happening to @Phil Sarin who posted the message immediately before this thread.
a
Just to be sure, you are creating the upstack branches from the branch that was set as trunk for the repo right? You can check this by looking at 
.graphite_repo_config
in the base of the repo directory. cc @Jacob Gold
e
@Aryaman I create the branches from the last branch con the stack. For example: from main: 
gt bc -m "test-1"
from test-1: 
gt bc -m "test-2"
… And yes, 
main
is my root branch on the 
.graphite_repo_config
p
same here. But I noticed that my file is in 
.git/.graphite_repo_config
instead of in the base directory of the repo.
Copy code
{
  "trunk": "main",
  "lastFetchedPRInfoMs": 1686591649605
}
e
mine as too is in 
.git/.graphite_repo_config
, I believe thats where it belongs
My team is able to stack PRs without problems, so is a problem with my config. I removed and reinstalled using brew. Still nothing
3 Views
Open in Slack
PreviousNext
Powered by