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

Update runs-on value in GitHub workflows #34787

Closed
wants to merge 1 commit into from

Conversation

tdupoiron
Copy link

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

Copy link

welcome bot commented Sep 30, 2024

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.

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

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

  • .github/workflows/add-review-template.yml
  • .github/workflows/alert-changed-branch-protections.yml
  • .github/workflows/all-documents.yml
  • .github/workflows/auto-close-dependencies.yml
  • .github/workflows/azure-preview-env-deploy-public.yml
  • .github/workflows/azure-preview-env-deploy.yml
  • .github/workflows/azure-preview-env-destroy.yml
  • .github/workflows/azure-prod-build-deploy.yml
  • .github/workflows/azure-staging-build-deploy.yml
  • .github/workflows/check-broken-links-github-github.yml
  • .github/workflows/check-for-spammy-issues.yml
  • .github/workflows/close-bad-repo-sync-prs.yml
  • .github/workflows/close-dangling-prs.yml
  • .github/workflows/close-on-invalid-label.yaml
  • .github/workflows/codeowners-content-strategy.yml
  • .github/workflows/codeowners-docs-engineering.yml
  • .github/workflows/codeowners-legal.yml
  • .github/workflows/codeql.yml
  • .github/workflows/comment-release-note-info.yml
  • .github/workflows/confirm-internal-staff-work-in-docs.yml
  • .github/workflows/content-changes-table-comment.yml
  • .github/workflows/content-lint-markdown.yml
  • .github/workflows/content-linter-rules-docs.yml
  • .github/workflows/copy-api-issue-to-internal.yml
  • .github/workflows/count-translation-corruptions.yml
  • .github/workflows/delete-orphan-translation-files.yml
  • .github/workflows/docs-review-collect.yml
  • .github/workflows/dont-delete-assets.yml
  • .github/workflows/dont-delete-features.yml
  • .github/workflows/enterprise-dates.yml
  • .github/workflows/enterprise-release-issue.yml
  • .github/workflows/expertise-required-label-message.yml
  • .github/workflows/first-responder-v2-prs-collect.yml
  • .github/workflows/generate-code-scanning-query-lists.yml
  • .github/workflows/headless-tests.yml
  • .github/workflows/hubber-contribution-help.yml
  • .github/workflows/index-autocomplete-elasticsearch.yml
  • .github/workflows/keep-caches-warm.yml
  • .github/workflows/link-check-daily.yml
  • .github/workflows/link-check-on-pr.yml
  • .github/workflows/lint-code.yml
  • .github/workflows/lint-entire-content-data-markdown.yml
  • .github/workflows/local-dev.yml
  • .github/workflows/main-preview-docker-cache.yml
  • .github/workflows/manually-purge-fastly.yml
  • .github/workflows/merged-notification.yml
  • .github/workflows/move-content.yml
  • .github/workflows/move-existing-issues-to-the-correct-repo.yml
  • .github/workflows/move-help-wanted-issues.yml
  • .github/workflows/move-ready-to-merge-pr.yaml
  • .github/workflows/move-reopened-issues-to-triage.yaml
  • .github/workflows/needs-sme-stale-check.yaml
  • .github/workflows/needs-sme-workflow.yml
  • .github/workflows/no-response.yaml
  • .github/workflows/notify-about-deployment.yml
  • .github/workflows/notify-when-maintainers-cannot-edit.yaml
  • .github/workflows/orphaned-features-check.yml
  • .github/workflows/orphaned-files-check.yml
  • .github/workflows/os-ready-for-review.yml
  • .github/workflows/package-lock-lint.yml
  • .github/workflows/purge-fastly.yml
  • .github/workflows/purge-old-deployment-environments.yml
  • .github/workflows/purge-old-workflow-runs.yml
  • .github/workflows/read-pr-doctolib.yml
  • .github/workflows/ready-for-doc-review.yml
  • .github/workflows/remove-fr-label-remove-from-fr-v2.yml
  • .github/workflows/repo-sync.yml
  • .github/workflows/site-policy-reminder.yml
  • .github/workflows/site-policy-sync.yml
  • .github/workflows/sme-review-tracking-issue.yml
  • .github/workflows/stale.yml
  • .github/workflows/sync-audit-logs.yml
  • .github/workflows/sync-codeql-cli.yml
  • .github/workflows/sync-graphql.yml
  • .github/workflows/sync-openapi.yml
  • .github/workflows/sync-search-elasticsearch.yml
  • .github/workflows/sync-search-pr.yml
  • .github/workflows/sync-secret-scanning.yml
  • .github/workflows/test-changed-content.yml
  • .github/workflows/test.yml
  • .github/workflows/triage-issue-comments.yml
  • .github/workflows/triage-issues.yml
  • .github/workflows/triage-pull-requests.yml
  • .github/workflows/triage-stale-check.yml
  • .github/workflows/triage-unallowed-contributions.yml
  • .github/workflows/validate-asset-images.yml
  • .github/workflows/validate-github-github-docs-urls.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.

@tdupoiron tdupoiron closed this Sep 30, 2024
@nguyenalex836 nguyenalex836 added invalid This issue/PR is invalid and removed triage Do not begin working on this issue until triaged by the team invalid This issue/PR is invalid labels Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants