What

Spend a bit of time looking at the github issues for the 3scale operator, Some are feature requests not bugs some are user issues i.e. configuration issues. and some have been responded to but there is no reply from the person who submitted the issue. I think we should start using labels to manage these issues and . We can add a labels for

• feature requests
• configuration
• needs-reply
  I would be good to get some automation around this as well like auto closing issue that don't get a response.

This may be worth implementing https://github.com/marketplace/actions/close-issues-after-no-reply to close issues that don't get responded to

• setup a test github org and test the functionality
• once satisfied it works as expected implement on 3scale-operator and apicast-operator repos , (may need assistance from someone with access to these repos)