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
In some projects, we have a stale.yml configuration like this:
daysUntilClose: false
staleLabel: stale
issues:
daysUntilStale: 60
markComment: >
This issue has been automatically marked as stale because it has not had
recent activity. It will be now be reviewed manually. Thank you
for your contributions.
pulls:
daysUntilStale: 7
markComment: >
This pull request has been automatically marked as stale because it has not had
recent activity. It will be now be reviewed manually. Thank you
for your contributions.
Is this what we would like to generalize?
The text was updated successfully, but these errors were encountered:
Isn't this config based on the now deprecated stale application?
If so, this should not become our convention 🤣 and we should configure a workflow action instead (but questions are same, do we automatically close stale issues and PR, how many days before considering an issue or a PR stale, which messages, ...).
In some projects, we have a
stale.yml
configuration like this:Is this what we would like to generalize?
The text was updated successfully, but these errors were encountered: