This message was deleted.
# bug-reports
s
This message was deleted.
a
@Jacob Gold is there someone that's able to help me with this? I'm not sure how to proceed and don't want to screw up a stack we've been working on for months 😆
j
hmm, we should sync that automatically. does repo sync fix the issue?
a
No
I assumed that it would be synced automatically
I just went through the process again, synced repo, restacked the stack, verified his changes are in his branch and tried to submit
This is his output
I've bee having him cancel here because I don't want our PRs messed up, any idea whats going on?
j
and that’s the exact same name as the remote branch?
a
yes
j
Hmm, well GH has an invariant that only one PR can open per branch/target at a time, so submitting as normal should be fine
a
Okay, we can try to do that and update you with the results
Should I have him run
gt track
or anything?
it seems like gt is just not tracking that the PR has been created
j
tracking is just for the branch, not the PR — from what I'm understanding, the branch is already tracked
a
yeah
dsg
seems to track it
and
gt log
shows the entire stack
It seems like theres an issue with his authentication
cant see PRs in gt dashboard or anything either
I suppose I'll have him try to add a personal access token. It's odd that none of us (to my knowledge) had to do that though
j
cant see PRs in gt dashboard or anything either
ah, it's this
a
Adding a PAT seems to have worked for the dash
j
the background fetch for PR data requires us to be authenticated, running repo sync again will trigger it as well
a
repo sync didn't work Adding a PAT seems to have worked for both his CLI and dashboard
idk if this is a bug with the oauth/github auth or what
j
I'm going to be improving the GitHub access settings page next week as part of our hackathon, there are weird edge cases with permissions/repo access that we don't surface well at the moment
a
❤️
Thanks! He's all set as of now, using the PAT
🔥 1