Skip to content

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

Closed
wants to merge 6 commits into from

Conversation

Sharra-writes
Copy link
Contributor

@Sharra-writes Sharra-writes commented Jun 5, 2025

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:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

Trying the stale workflow from desktop/desktop to make sure it's a script problem not a yaml problem.
@Copilot Copilot AI review requested due to automatic review settings June 5, 2025 17:32
Copy link

welcome bot commented Jun 5, 2025

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.

Copy link
Contributor

@Copilot Copilot AI left a 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 workflow name
  • Switched to actions/stale@v9 and introduced start-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 and stale-pr-message parameters under with: to provide clear, custom notifications when issues or PRs are marked stale.
with:

Copy link
Contributor

github-actions bot commented Jun 5, 2025

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

  • .github/workflows/stale.yml

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process. :octocat:

The complete list of files we can't accept are:

  • .devcontainer/**
  • .github/**
  • data/reusables/rai/**
  • Dockerfile*
  • src/**
  • package*.json
  • content/actions/deployment/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter type: rai.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jun 5, 2025
@Sharra-writes Sharra-writes requested a review from janiceilene June 5, 2025 17:38
@Sharra-writes Sharra-writes added content This issue or pull request belongs to the Docs Content team github_actions Pull requests that update GitHub Actions code and removed triage Do not begin working on this issue until triaged by the team labels Jun 5, 2025
Copy link
Contributor

github-actions bot commented Jun 5, 2025

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 links

Note: 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.

Copy link
Contributor

github-actions bot commented Jun 5, 2025

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

  • .github/workflows/stale.yml

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process. :octocat:

The complete list of files we can't accept are:

  • .devcontainer/**
  • .github/**
  • data/reusables/rai/**
  • Dockerfile*
  • src/**
  • package*.json
  • content/actions/deployment/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter type: rai.

Copy link
Contributor

github-actions bot commented Jun 5, 2025

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

  • .github/workflows/stale.yml

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process. :octocat:

The complete list of files we can't accept are:

  • .devcontainer/**
  • .github/**
  • data/reusables/rai/**
  • Dockerfile*
  • src/**
  • package*.json
  • content/actions/deployment/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter type: rai.

Updating permissions. Not sure how this is being used elsewhere without those permissions.
Copy link
Contributor

github-actions bot commented Jun 5, 2025

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

  • .github/workflows/stale.yml

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process. :octocat:

The complete list of files we can't accept are:

  • .devcontainer/**
  • .github/**
  • data/reusables/rai/**
  • Dockerfile*
  • src/**
  • package*.json
  • content/actions/deployment/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter type: rai.

@Sharra-writes
Copy link
Contributor Author

Need to look into this more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team github_actions Pull requests that update GitHub Actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant