# GitHub Issues Migration is coming soon

**URL:** <https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791>\
**Category:** Core Development\
**Created:** [February 18, 2022, 8:54pm UTC](https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791 "2022-02-18T20:54:54Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)\
**Post date:** [February 21, 2022, 12:08pm UTC](https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791/14 "2022-02-21T12:08:27Z")

</div>

> [@ambv](#):
>
> Each issue that currently exists on BPO will include metadata indicating where it was moved on Github

I’m in the nosy list of 885 BPO issues. Should I expect 885 emails, or can you disable sending email notifications to all users of the 40k+ issues?

---

_[View the full topic](https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791)._