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
Has any thought gone into adding support for moderating GitHub Discussions and labelling them as stale and closing them? I notice that there only appears to be support for using the GraphQL API for Discussions rather than the REST api. Whilst it appears that it would support the mutations needed to list / comment / close/resolve the discussions, it doesn't immediately appear that it has a way of adding labels to them (even though that is supported by the web ui which makes a FORM POST to /org/repo/discussions/labels?number=1234 to add/remove labels)
Justification:
Discussions can fill up with unanswered questions/threads over time and it would be useful to keep them healthy with stale processing in the same way as issues and pull requests
The text was updated successfully, but these errors were encountered:
@dnwe As this seems to be rather stale (sorry for my bad joke), I've decided to create this: https://github.com/marketplace/actions/stalesweeper, first official release is now ready and tested and should solve all listed scenarios :) Hope you'll give it a try and maybe a star.
Description:
Has any thought gone into adding support for moderating GitHub Discussions and labelling them as stale and closing them? I notice that there only appears to be support for using the GraphQL API for Discussions rather than the REST api. Whilst it appears that it would support the mutations needed to list / comment / close/resolve the discussions, it doesn't immediately appear that it has a way of adding labels to them (even though that is supported by the web ui which makes a FORM POST to
/org/repo/discussions/labels?number=1234
to add/remove labels)Justification:
Discussions can fill up with unanswered questions/threads over time and it would be useful to keep them healthy with stale processing in the same way as issues and pull requests
The text was updated successfully, but these errors were encountered: