This message was deleted.

I’ve run

gt ss

locally and all changes have been successfully pushed to the remote branches

That's so weird, sorry this is happening! cc @Greg

I have the same!

Hm, sorry @Pranav Kunapuli @Georgie! Can you try running

gt ss --always

on your stack (using the latest CLI version) and see if that fixes? It will push your stack and all deps to graphite, hopefully fixing the remote state

Just tried it, no change! CLI still shows a stack and Dashboard shows no stack. Let me know if there are any other details I can share that would help with diagnosis!

Same here ☹️

hm, thanks for trying that! Let me loop in @Jacob Gold who is our resident expert at PR dependencies

@Jacob Gold @Greg I’m still seeing the “Not on default branch” issue in the dashboard. Any other steps I can try on my end to resolve this?

Plus one on "Are there any other steps I can try to resolve this?". This has become quite painful as it is affecting every stack I create!

Hi guys, sorry this is still happening! Let me get someone to look into this

Yes we did! I do see the old name when I run

gt repo name

Ah that makes sense - we're having an issue with syncing renamed repositories in the dashboard, @Nicholas Yan or @Brendan Ngo should be able to fix this on a case-by-case basis for y'all while we iron out that issue

It might also be worth mentioning that I don’t have a local

.graphite_repo_config

file in this repository. My guess is that when I ran

gt repo init

~5 months ago this config file didn’t exist. I tried re-running that command but no config file was generated. Should we try manually creating this file? If so, what structure/values should I use?

that file lives in the

.git

folder

Ah okay, found it now

Broadly — you shouldn't need to ever edit that file manually

@Pranav Kunapuli do you mind messaging me what the repo was renamed to and from?

Yes! We did rename ours too, but I'm the only person in our team who is having this issue!

@Georgie let me know if you need help resolving also! you can dm me what the repo was renamed to and from and I can investigate. we're also working on a longer term solution that can handle repo name changes so that these problems don't happen in the future

Hey there, just reporting that I’m getting the same issue and there was no repo renaming involved. re-submitting with

--always

didn’t fix, and I’m running on 0.20.15. Is there any fix I can do to get this resolved?