You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if this action could be altered to close issues, which do not follow the actual body of the template.
Not everyone wants to have a pre-defined title for issues (like me) and some people may alter the title, but still follow the general template, so closing the issue for just altering the title would be quite rude.
If possible should the action be able to compare template with issue body.
The only issue I see so far would be to look for user-input (the comments they make) and perhaps for checklists being checked (- [x] text)
For the text could the template itself perhaps contain a invisible placeholder using <!-- text --> to tell it, where user-input would be.
Like:
> Please provide your info here<!-- INPUT:START --><!-- INPUT:END -->
I'm really interested in using this action, but the aforementioned limitation makes it quite useless for my cases, so I hope there can be a future solution for this.
The text was updated successfully, but these errors were encountered:
I was wondering if this action could be altered to close issues, which do not follow the actual body of the template.
Not everyone wants to have a pre-defined title for issues (like me) and some people may alter the title, but still follow the general template, so closing the issue for just altering the title would be quite rude.
If possible should the action be able to compare template with issue body.
The only issue I see so far would be to look for user-input (the comments they make) and perhaps for checklists being checked (
- [x] text
)For the text could the template itself perhaps contain a invisible placeholder using
<!-- text -->
to tell it, where user-input would be.Like:
I'm really interested in using this action, but the aforementioned limitation makes it quite useless for my cases, so I hope there can be a future solution for this.
The text was updated successfully, but these errors were encountered: