Disabled issues on forked repo - expected or a bug?

[proeugene]

Hi! Loving the London workshop that's happening at the moment of writing this comment, thank you all the guys from GitHub who are here today who help to make it happen!

I had a small issue with this repo whilst following the exercises here here, specifically in "Exercise 1A: Assign an Issue to Copilot".

I forked the repo, and discovered that "Issues" were disabled on this repo, and had to enable them manually in order to complete the exercise. Before I knew that "Issues" were disabled for this forked repo, I tried manually going to Issues by tweaking the URL of the repo and appending /issues, which did let me see an empty list of issues, and even let me type in title and description of a new issue, but then resulted in the error in the end, which is when I figured out that Issues were disabled on this repo.

I'm not sure if this is a standard behaviour in forked repos, but considering the exercise 1A description didn't mention this, I thought I'd highlight it, in case anyone else struggles with this in the future, even though this is only a minor thing.

Thanks!