Hi Eric,

Just to emphasize one of Magnus's points: check and make sure that your git
remote is "[email protected]:yourname/ghc". If it starts with "https://";
then you might need PATs, and you probably don't want that.

(https:// urls probably worked in more cases in the past. Now that all
projects are internal by default, I suspect they require extra hoops.)

-Bryan

On Mon, 3 Aug 2026 at 13:47, Magnus Viernickel via ghc-devs <
[email protected]> wrote:

> Hi Eric,
>
> Why do you need an access token to check out and fetch GHC? I don't
> think you regularly do; best you clone GHC via SSH, but since your fork
> is public anyway, you should at least be able to fetch your fork without
> any access tokens.
>
> That being said, I will assume that the reason why you don't get an
> access token is that an XHR request failed due to Anubis, our spam
> protection. Usually that will resolve itself after doing a hard refresh
> of the page.
>
> If your issues persist, please share your user name and address me
> directly at this mail address so I can help you.
>
> Best
>
> Magnus
>
> On 8/3/26 12:10, Eric via ghc-devs wrote:
> > Hi all,
> >
> > In order to fetch and checkout a branch of my fork of GHC, I am trying
> > to create a personal access token which I would use as a password at
> > the command line. However, when I try to add a new token, the page
> > hangs displaying a the "please wait" circle graphic. Does anyone know
> > what might be wrong?
> >
> > Regards,
> > Eric
> > _______________________________________________
> > ghc-devs mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
> _______________________________________________
> ghc-devs mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
ghc-devs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to