This message was deleted.
# how-do-i
s
This message was deleted.
j
if feature-part-2 already correctly contains feature-part-1 in its history,
gt downstack track feature-part-2
will do the trick — if not, you'll need to
git rebase feature-part-1 feature-part-2
first
j
the branch says its already tracked but when I check the pr(s) on graphite they are showing as separate (not part of the same stack)
j
ah, then the issue is likely not with the CLI, but an issue with the data on our end — sometimes, repo renames can result in this behavior. you may need to configure
gt repo owner
and
gt repo name
to match what GitHub has (https://graphite.dev/docs/cli-configuration#github-repository-information) e.g. for withgraphite/my-repo I would run
gt repo owner --set withgraphite && gt repo name --set my-repo
and then you can submit your stack again with
gt stack submit --always
to ensure the stack data gets corrected.
if that doesn't fix the issue, then there may be some deeper issue on our end that I can look into
j
Running
gt stack submit --always
seemed to fix it
thx!
j
no problem!