As said by the title, I was observing a closed issue in open issues list. It seems to be also on the GitHub API, since I also reproduce this on third party GitHub client (such as FastHub). I think it’s likely to be a bug. Since this repository has been renamed before, it could be the rename process that caused this bug.
Thanks for being here! It appears the issue is resolved now.
Thanks. I can confirm on my side that it’s fixed.