A test issue, please ignore

[bob-the-hamster]

this is a test issue

[bob-the-hamster]

this is a test comment on a test issue

[ohrrpgce-githubmail]

Alright! We finally have integration between the github issue tracker https://github.com/ohrrpgce/ohrrpgce/issues/ with the mailing list

…

On Sun, Jul 28, 2019 at 1:22 PM James Paige ***@***.***> wrote: this is a test comment on a test issue — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=AMWGWZSXHRVR34I4L7ILA5LQBXIRRA5CNFSM4IHM7YO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD27C2RQ#issuecomment-515779910>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMWGWZUQ2FKI3K47BOFSO53QBXIRRANCNFSM4IHM7YOQ> . _______________________________________________ Ohrrpgce mailing list ***@***.*** http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org

[bob-the-hamster]

closing this test bug, it has served its purpose

[rversteegen]

Eeek! Just last night before bed I noticed your comments on bug #1 a week ago, which I had missed because I wasn't actually subscribed to this repo! I was going to bring up subscribing the mailing list. So is creating a new github account and subscribing it the only way to get emails sent to a mailing list?

And I wonder, am I going to have to now unwatch this repo (with my personal GH account) to avoid duplicate emails?

I also just noticed the ability to transfer issues from one repo to another. Maaaybe I will rename this repo, create a new ohrrpgce project, import the bugzilla and sf bugs into it, then transfer all the issues from this repo to the new one. I see I will just need to manually re-apply the labels on these 21 issues. It is possible to rename a repo and replace it with another one of the same name.

[bob-the-hamster]

On Sun, Jul 28, 2019, 10:39 PM Ralph Versteegen ***@***.***> wrote: Eeek! Just last night before bed I noticed your comments on bug #1 <#1> a week ago, which I had missed because I wasn't actually subscribed to this repo! I was going to bring up subscribing the mailing list. So is creating a new github account and subscribing it the only way to get emails sent to a mailing list?

Yes, I created a separate GitHub account with a separate email that forwards to the list. And I wonder, am I going to have to now unwatch this repo (with my personal

GH account) to avoid duplicate emails?

I don't think so... At any rate, I have not been getting duplicates. I also just noticed the ability to transfer issues from one repo to

…

another. Maaaybe I will rename this repo, create a new ohrrpgce project, import the bugzilla and sf bugs into it, then transfer all the issues from this repo to the new one. I see I will just need to manually re-apply the labels on these 21 issues. It is possible <https://help.github.com/en/articles/renaming-a-repository> to rename a repo and replace it with another one of the same name. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=AA2IR6MHTM6MBCMTADUW3NLQBZJ5XA5CNFSM4IHM7YO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD27NVGA#issuecomment-515824280>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2IR6POUKWAXILK7T7SQZDQBZJ5XANCNFSM4IHM7YOQ> .

[rversteegen]

Well, I got a couple duplicate emails from this thread -- but not from every comment.

Oh, I also clicked the "mute this thread" link in on of the emails to see what would happen, and I got a message that I had muted the thread... but it isn't actually muted for me, does that apply to the ohrrpgce-githubmail account? Apparently not, because your latest comment ended up in the archives for the mailinglist, although I didn't get that email from the mailing list. I guess because it was a duplicate email that gmail filtered out? I don't know whether it filters duplicates from mailinglist.

I also notice that emails from ohrrpgce-githubmail forwarded by the mailinglist have two reply-to addresses, github and the mailinglist, which is interesting and useful.

[bob-the-hamster]

I can't decide if this is working perfectly, or a big ol' mess... But it is definitely better than nothing I guess ;)

…

On Mon, Jul 29, 2019, 8:57 AM Ralph Versteegen ***@***.***> wrote: Well, I got a couple duplicate emails from this thread -- but not from every comment. Oh, I also clicked the "mute this thread" link in on of the emails to see what would happen, and I got a message that I had muted the thread... but it isn't actually muted for me, does that apply to the ohrrpgce-githubmail account? Apparently not, because your latest comment ended up in the archives for the mailinglist, although I didn't get that email from the mailing list. I guess because it was a duplicate email that gmail filtered out? I don't know whether it filters duplicates from mailinglist. I also notice that emails from ohrrpgce-githubmail forwarded by the mailinglist have two reply-to addresses, github and the mailinglist, which is interesting and useful. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=AA2IR6M6N3AQ5BKUHVIGGVTQB3SNLA5CNFSM4IHM7YO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3ATY2Y#issuecomment-515980395>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2IR6L3GYJLQVJZWZRH623QB3SNLANCNFSM4IHM7YOQ> .