A few days ago you noticed that I keep adding SSH deploy keys to the VsCoq repo. The better alternative is fine-grained personal access tokens, but you have to enable them in the coq-community organization. Could anyone please do that? Screenshot-from-2022-11-18-01-24-14.png
The next step in the wizard will ask you to choose whether to require approval or not. Since I always delete the token when I'm done pushing, you should choose not to require approval. Screenshot-from-2022-11-18-01-27-36.png
@Théo Zimmermann I'm fine with enabling personal access tokens in Coq-Community org. So I'll leave the final decision/fiddling to you.
Done. Thanks @Huỳnh Trần Khanh for looking into this!
FTR, the next step in the process asked whether to also enable access through classic (unscoped) PAT. I've also set it to true since I think this is the legacy behavior (it used to be allowed) and I wouldn't want to break existing workflows by changing this setting, but we should look into disabling access via classic PAT in the future (since fine-grained PAT are a strict improvement over this).
I'll move this thread since it is a generic coq-community discussion and not specific to the VsCoq repo.
This topic was moved here from #VsCoq devs & users > Enable fine-grained access tokens by Théo Zimmermann.
Last updated: Jun 06 2023 at 22:01 UTC