On Mon, Sep 12, 2022 at 6:53 AM Marc Mezzarobba <m...@mezzarobba.net> wrote: > > Dima Pasechnik wrote: > > this script goes for a simpler route - it writes GitHub logins (or > > original trac logins for the cases where there is no match) of users > > who commented, etc. into > > comments text. This does not need authorisation from users, but it's > > arguably less nice looking. > > Not just less nice looking: it means for instance that you will not be > able to search for all tickets/issues you reported both before and > after the migration with a single, simple query. Or am I missing > something?
Not sure about "a single, simple" query which won't need to be some kind of script, e.g. "search for the 1st @baz in the 1st comment in all issues" would give you all issues opened by @baz". Probably doable, though. Ideally, we'd create these issues/comments using GH user access tokens - unfortunately they, in their default form, don't allow a restriction to a particular repo. However, https://micahjon.com/2021/repo-scoped-access-token-for-github-org/ seems to describe a process to get repo-restricted tokens we'd rather use. Or we can indeed contact GitHub for help with these sorts of tokens for all GitHub users in sagemath organisation. Dima > > -- > Marc > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/tfmhgf%2412cv%241%40ciao.gmane.io. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq1wp9hOiNf9SVSb0%3DbMJbmHkYL8wyec%2BXu-U4rabvhHhw%40mail.gmail.com.
