Don't check whether issues are enabled for forks. If the current repo is a fork, and issues aren't enabled, don't fail.
When you ask GitHub whether or not issues are enabled, also check whether it's a fork. If it's a fork, remove the "issues not enabled" message and don't fail.
Just turn it into a warning.
Make sure you have read the issue guidelines and that you filled out the entire template.
The action is used for /default
It needs to fail there
Could there be an env var to just disable it?
Yes, but before I change it, I want to convert it to a composite action
What do you mean? What would it have?

Takes time to convert...
So is there anything stopping this from getting beta tested by people?
Well, it's only 10% done, so there is that? :smile:
Will probably have converted enough later this week to publish it as a beta action aimed at replacing the current.
Sounds good. By the way, you might be able to make any clones quicker with --single-branch, --branch, and --fetch-depth.
At the point of cloning I don't know the branch, depth I already have for all of them, but sure :+1:
It's not the cloning that takes time, it's running hassfest and HACS load test :smile:
The new action does currently not check fork at all, I'll reserve that to the hacs/default repo instead :+1:
https://github.com/marketplace/actions/hacs-action
Sounds good! Why would you want to do the requirements check? Python builtins can be very useful.
Builtins are fine, using 3.party imports that overwrites them, not so much
And what exactly does this mean?
✅ This day ends with an 'y' (Sunday)
That this day ends with the character 'y'
Why does it check for that?
1) It does not check
2) For fun
Most helpful comment
Well, it's only 10% done, so there is that? :smile:
Will probably have converted enough later this week to publish it as a beta action aimed at replacing the current.