Issues with Github remote origins not being able to be found

Coding with ChatGPT
1

Hi,

So I have been using codex to help me build further on a intrasite for the company I work for.
It seems to be able to find the codebase, because it knows how to answer certain things. But whenever I ask it to update itself using remote origins of the git branch master it tells me there aren’t any. But I know they exist.

[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
[remote “origin”]
url = git@github.com:Aquaengraved/xxx.git
fetch = +refs/heads/:refs/remotes/origin/
[branch “master”]
remote = origin
merge = refs/heads/master

Actual remotes (xxx are placeholders):
PS W:\site_monitoring> git remote -v
origin git@github dot com:Aquaengraved/xxx.git (fetch)
origin git@github dot com:Aquaengraved/xxx.git (push)
PS W:\site_monitoring>

How can it be that it cannot find the remotes when they clearly exist?
What am I missing here or doing wrong?

What it tells me:

The image shows a terminal session demonstrating that a local Git repository has minimal settings configured, no remote repositories defined, and only master and work branches available. (Captioned by AI)
The image shows a terminal session demonstrating that a local Git repository has minimal settings configured, no remote repositories defined, and only master and work branches available. (Captioned by AI)719×665 20.5 KB

2

Solved it. I did not realize it was mandatory to use the setup script and a PAT token to allow it to use my remote branches. I figured that through github authorization this was already available in the environment.

For anyone else in the future running into this, below is what I configured to get it working:

The image shows a development environment setup, including generating a fine-grained GitHub personal access token, setting environment variables with the token, specifying domain allowlists, and a terminal window displaying setup logs and runtime configurations. (Captioned by AI)
The image shows a development environment setup, including generating a fine-grained GitHub personal access token, setting environment variables with the token, specifying domain allowlists, and a terminal window displaying setup logs and runtime configurations. (Captioned by AI)1781×799 83.6 KB

Turned out to be fairly simple. It was just not realizing it was required on my end.
Sorry!