Skip to content
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

Rename no-response. #36131

Closed
wants to merge 2 commits into from
Closed

Rename no-response. #36131

wants to merge 2 commits into from

Conversation

Weera1234
Copy link

Why:

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 preview environment.

Copy link
Contributor

github-actions bot commented Feb 1, 2025

🚀 Manual Deployment Required

It looks like this pull request contains code changes. To preview these changes, an internal Hubber will need to manually deploy the changes to one of our staging servers.

Thank you for your contribution!

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Feb 1, 2025
Copy link
Contributor

github-actions bot commented Feb 1, 2025

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

  • .github/workflows/no-response.yam
  • .github/workflows/no-response.yaml

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 Feb 1, 2025

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

  • .github/workflows/no-response.yam
  • .github/workflows/no-response.yaml

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.

@subatoi subatoi added invalid This issue/PR is invalid and removed triage Do not begin working on this issue until triaged by the team labels Feb 3, 2025
@github-actions github-actions bot closed this Feb 3, 2025
@Weera1234 Weera1234 deleted the patch-3 branch February 4, 2025 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This issue/PR is invalid
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants