-
Notifications
You must be signed in to change notification settings - Fork 62k
Replace stale.yml with the workflow from another repo #38763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Trying the stale workflow from desktop/desktop to make sure it's a script problem not a yaml problem.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This pull request replaces the existing stale workflow configuration with the version from another repository, updating schedule timing, action version, and label handling parameters.
- Updated
on.schedule
cron timing and workflowname
- Switched to
actions/stale@v9
and introducedstart-date
plus never-close flags - Adjusted label parameters for stale issues and exempt labels
Comments suppressed due to low confidence (2)
.github/workflows/stale.yml:58
- The
stale-issue-label
parameter may only support a single label string; combining labels with a comma could prevent any label from being applied. Separate multiple labels into distinct parameters or confirm the action supports comma-separated lists.
stale-issue-label: 'stale, triage'
.github/workflows/stale.yml:40
- [nitpick] Consider adding
stale-issue-message
andstale-pr-message
parameters underwith:
to provide clear, custom notifications when issues or PRs are marked stale.
with:
Co-authored-by: Copilot <[email protected]>
👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:
You'll need to revert all of the files you changed that match that list using GitHub Desktop or The complete list of files we can't accept are:
We also can't accept contributions to files in the content directory with frontmatter |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. This pull request contains code changes, so we will not generate a table of review links. 🤖 This comment is automatically generated. |
👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:
You'll need to revert all of the files you changed that match that list using GitHub Desktop or The complete list of files we can't accept are:
We also can't accept contributions to files in the content directory with frontmatter |
👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:
You'll need to revert all of the files you changed that match that list using GitHub Desktop or The complete list of files we can't accept are:
We also can't accept contributions to files in the content directory with frontmatter |
Updating permissions. Not sure how this is being used elsewhere without those permissions.
👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:
You'll need to revert all of the files you changed that match that list using GitHub Desktop or The complete list of files we can't accept are:
We also can't accept contributions to files in the content directory with frontmatter |
Need to look into this more. |
Trying the stale workflow from desktop/desktop to make sure it's a script problem not a yaml problem.
I don't know if this will work properly, our stale workflow has a lot of values and checks this doesn't, but I guess the worst it can do is fail.
Why:
Our stale check isn't working right.
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following: