Stream: coq-community devs & users

Topic: Enable fine-grained access tokens


view this post on Zulip Huỳnh Trần Khanh (Nov 18 2022 at 01:26):

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

view this post on Zulip Huỳnh Trần Khanh (Nov 18 2022 at 01:29):

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

view this post on Zulip Karl Palmskog (Nov 18 2022 at 08:47):

@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.

view this post on Zulip Théo Zimmermann (Nov 18 2022 at 08:55):

Done. Thanks @Huỳnh Trần Khanh for looking into this!

view this post on Zulip Théo Zimmermann (Nov 18 2022 at 08:56):

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).

view this post on Zulip Théo Zimmermann (Nov 18 2022 at 08:57):

I'll move this thread since it is a generic coq-community discussion and not specific to the VsCoq repo.

view this post on Zulip Notification Bot (Nov 18 2022 at 08:58):

This topic was moved here from #VsCoq devs & users > Enable fine-grained access tokens by Théo Zimmermann.


Last updated: Feb 04 2023 at 03:30 UTC