On 6/17/22 5:23 AM, Adi Roiban wrote:
Hi Patrick,
On Thu, 16 Jun 2022 at 20:08, Patrick Cloke<[email protected]> wrote:
Hi Adi,
Thanks for working on this -- taking a look at the issues that get
generated I can see my comments coming across in some (e.g.
https://github.com/twisted/twisted-trac-migration-2/issues/8928) but I'm
surprised that I didn't end up on GitHub's subscribed list for the
issue, even though they @clokep. Is this just a quirk of the import and
will we need to search the meta-data / re-subscribe to any issues after
the migration is complete?
This is the limitation of the bulk import API.
We can't impersonate other GitHub accounts, and can only take limited
actions on behalf of the Twisted GitHub team members.
We can't use the API to subscribe random accounts.
You can only subscribe if you are watching the repo or if you
explicitly left a comment on that GitHub issues.
But all the comments so far are left by the import "twisted-trac" account.
That makes sense, thanks for the explanation. I guess naively i was
expecting issues I was @-ed on would still result in a subscription to
that issue /after/ the import finished.
You need to search for cc__clokep
We were not able to use a single underscore or dash as GitHub has
extra processing for these characters, and consider them word-breaks.
Oh I had missed that there was a double underscore there. Thanks!
Looks like it will be easy enough to re-subscribe to things than afterward.
Thanks so much for your explanation (and work on this)! Looking forward
to using a single platform for Twisted.
--Patrick
_______________________________________________
Twisted mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/twisted.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/2AMYT7AA3UEC7FVULMM4QZFEJFUSKZIY/
Code of Conduct: https://twisted.org/conduct
