Fix closing answered issues by setting the stale-issue-message attribute

[jasongrout]

References

Follow-up to #10536 after noticing that the closures are still not happening.

Code changes

We are seeing an error that prevents issues from getting marked as closing (https://github.com/jupyterlab/jupyterlab/runs/2994705101?check_suite_focus=true#step:2:3995):

[#5869] Skipping this issue because it should be marked as stale based on the option days-before-stale (​https://github.com/actions/stale#days-before-stale​) (30) but the option stale-issue-message (​https://github.com/actions/stale#stale-issue-message​) is not set

In the upcoming action version 4, we can omit both the skip-stale-issue-message and the stale-issue-message.

User-facing changes

Backwards-incompatible changes

[jupyterlab-dev-mode]

Thanks for making a pull request to JupyterLab!

To try out this branch on binder, follow this link:

[jasongrout]

I filed an issue with the action at actions/stale#521.

It seems the skip-stale-issue-message option was removed in actions/stale#457

[jasongrout]

Update: it looks like we still need the skip option until the action releases v4.

[blink1073]

Thanks!

[jasongrout]

This change didn't seem to work: https://github.com/jupyterlab/jupyterlab/runs/3004704380?check_suite_focus=true#step:2:4019

[jasongrout]

On the other hand, interestingly, this run from this morning (several hours after this PR was merged) does not indicate that the stale-issue-message was set: https://github.com/jupyterlab/jupyterlab/runs/3004704380?check_suite_focus=true#step:2:2

Maybe we'll let it run another day or two to see about picking up this change?

[jasongrout]

If this change does not end up working, then I think we should just wait for the upcoming v4 of this action that removes this error and streamlines this api.