[![Close bad repo-sync PRs](https://github.com/github/docs/actions/wo…

[kyc-theresawchavez789]

…rkflows/close-bad-repo-sync-prs.yml/badge.svg?event=create)](https://github.com/github/docs/actions/workflows/close-bad-repo-sync-prs.yml)

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

[github-actions]

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

• .github/workflows/moda-ci.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.

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]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment
• Message #docs-engineering on Slack for a staging server.

A Hubber will need to deploy your changes internally to review.

Table of review links

⚠️ Warning: Our review server is experiencing latency issues.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.