Skip to content

Rename verifying-or-approving-a-domain-for-your-organization.md to ve… - #45263

Open
clauderiks wants to merge 69 commits into
github:mainfrom
clauderiks:patch-1
Open

Rename verifying-or-approving-a-domain-for-your-organization.md to ve…#45263
clauderiks wants to merge 69 commits into
github:mainfrom
clauderiks:patch-1

Conversation

@clauderiks

@clauderiks clauderiks commented Jul 23, 2026

Copy link
Copy Markdown

…rifying-or-approving-a-domain-for-your-organization.md

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.

SandboxCodeX and others added 30 commits July 13, 2026 02:14
Rename advanced-security-must-be-enabled.md to advanced-security-must-be-enabled.md
…uong0507-hub/patch-5

Rename CODE_OF_CONDUCT.md to CODE_OF_CONDUCT.md
…uong0507-hub/patch-6

Rename govern-for-adoption.md to govern-for-adoption.md
…uong0507-hub/patch-7

Rename events-that-trigger-workflows.md to events-that-trigger-workflows.md
…uong0507-hub/patch-8

Rename apps.md to apps.md
…uong0507-hub/patch-9

Rename review-comment.yml to review-comment.yml
…huong0507-hub/patch-10

Rename find-matching-code.md to find-matching-code.md
…huong0507-hub/patch-1

Rename advanced-security-must-be-enabled.md to advanced-security-must-be-enabled.md
…huong0507-hub/patch-4

Rename index.md to index.md
…huong0507-hub/patch-7

Rename events-that-trigger-workflows.md to events-that-trigger-workflows.md
…huong0507-hub/patch-3

Merge pull request nguyenvanhoaithuong0507-hub#12 from nguyenvanhoaithuong0507-hub/patch-4

Rename index.md to index.md
…huong0507-hub/patch-8

Rename apps.md to apps.md
…huong0507-hub/patch-6

Rename govern-for-adoption.md to govern-for-adoption.md
…huong0507-hub/patch-9

Rename review-comment.yml to review-comment.yml
…huong0507-hub/patch-6

Rename govern-for-adoption.md to govern-for-adoption.md
SandboxCodeX and others added 18 commits July 18, 2026 07:47
…huong0507-hub/patch-9

Rename review-comment.yml to review-comment.yml (nguyenvanhoaithuong0507-hub#37)

<!--
Thank you for contributing to this project! You must fill out the
information below before we can review this pull request. By explaining
why you're making a change (or linking to an issue) and what changes
you've made, we can triage your pull request to the best possible team
for review.
-->

### Why:

<!-- Paste the issue link or number here -->
Closes: 

<!-- If there's an existing issue for your change, please link to it
above.
If there's _not_ an existing issue, please open one first to make it
more likely that this update will be accepted:
https://github.com/github/docs/issues/new/choose. -->

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

<!-- Let us know what you are changing. Share anything that could
provide the most context.
If you made changes to the `content` directory, a table will populate in
a comment below with links to the review and current production
articles. -->

### 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](http://docs.github.com/en/contributing/writing-for-github-docs/about-githubs-documentation-fundamentals).
- [ ] All CI checks are passing and the changes look good in the review
environment.
Signed-off-by: SandboxCodeX <253301533+nguyenvanhoaithuong0507-hub@users.noreply.github.com>
<!--
Thank you for contributing to this project! You must fill out the
information below before we can review this pull request. By explaining
why you're making a change (or linking to an issue) and what changes
you've made, we can triage your pull request to the best possible team
for review.
-->

### Why:

<!-- Paste the issue link or number here -->
Closes: 

<!-- If there's an existing issue for your change, please link to it
above.
If there's _not_ an existing issue, please open one first to make it
more likely that this update will be accepted:
https://github.com/github/docs/issues/new/choose. -->

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

<!-- Let us know what you are changing. Share anything that could
provide the most context.
If you made changes to the `content` directory, a table will populate in
a comment below with links to the review and current production
articles. -->

### 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](http://docs.github.com/en/contributing/writing-for-github-docs/about-githubs-documentation-fundamentals).
- [ ] All CI checks are passing and the changes look good in the review
environment.

Merge pull request nguyenvanhoaithuong0507-hub#17 from nguyenvanhoaithuong0507-hub/patch-9

Rename review-comment.yml to review-comment.yml (nguyenvanhoaithuong0507-hub#37)

<!--
Thank you for contributing to this project! You must fill out the
information below before we can review this pull request. By explaining
why you're making a change (or linking to an issue) and what changes
you've made, we can triage your pull request to the best possible team
for review.
-->

### Why:

<!-- Paste the issue link or number here -->
Closes: 

<!-- If there's an existing issue for your change, please link to it
above.
If there's _not_ an existing issue, please open one first to make it
more likely that this update will be accepted:
https://github.com/github/docs/issues/new/choose. -->

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

<!-- Let us know what you are changing. Share anything that could
provide the most context.
If you made changes to the `content` directory, a table will populate in
a comment below with links to the review and current production
articles. -->

### 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](http://docs.github.com/en/contributing/writing-for-github-docs/about-githubs-documentation-fundamentals).
- [ ] All CI checks are passing and the changes look good in the review
environment.
<!--
Thank you for contributing to this project! You must fill out the
information below before we can review this pull request. By explaining
why you're making a change (or linking to an issue) and what changes
you've made, we can triage your pull request to the best possible team
for review.
-->

### Why:

<!-- Paste the issue link or number here -->
Closes: 

<!-- If there's an existing issue for your change, please link to it
above.
If there's _not_ an existing issue, please open one first to make it
more likely that this update will be accepted:
https://github.com/github/docs/issues/new/choose. -->

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

<!-- Let us know what you are changing. Share anything that could
provide the most context.
If you made changes to the `content` directory, a table will populate in
a comment below with links to the review and current production
articles. -->

### 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](http://docs.github.com/en/contributing/writing-for-github-docs/about-githubs-documentation-fundamentals).
- [ ] All CI checks are passing and the changes look good in the review
environment.
<!--
Thank you for contributing to this project! You must fill out the
information below before we can review this pull request. By explaining
why you're making a change (or linking to an issue) and what changes
you've made, we can triage your pull request to the best possible team
for review.
-->

### Why:

<!-- Paste the issue link or number here -->
Closes: 

<!-- If there's an existing issue for your change, please link to it
above.
If there's _not_ an existing issue, please open one first to make it
more likely that this update will be accepted:
https://github.com/github/docs/issues/new/choose. -->

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

<!-- Let us know what you are changing. Share anything that could
provide the most context.
If you made changes to the `content` directory, a table will populate in
a comment below with links to the review and current production
articles. -->

### 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](http://docs.github.com/en/contributing/writing-for-github-docs/about-githubs-documentation-fundamentals).
- [ ] All CI checks are passing and the changes look good in the review
environment.
<!--
Thank you for contributing to this project! You must fill out the
information below before we can review this pull request. By explaining
why you're making a change (or linking to an issue) and what changes
you've made, we can triage your pull request to the best possible team
for review.
-->

### Why:

<!-- Paste the issue link or number here -->
Closes: 

<!-- If there's an existing issue for your change, please link to it
above.
If there's _not_ an existing issue, please open one first to make it
more likely that this update will be accepted:
https://github.com/github/docs/issues/new/choose. -->

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

<!-- Let us know what you are changing. Share anything that could
provide the most context.
If you made changes to the `content` directory, a table will populate in
a comment below with links to the review and current production
articles. -->

### 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](http://docs.github.com/en/contributing/writing-for-github-docs/about-githubs-documentation-fundamentals).
- [ ] All CI checks are passing and the changes look good in the review
environment.
Bumps the npm_and_yarn group with 4 updates in the / directory: [js-yaml](https://github.com/nodeca/js-yaml), [axios](https://github.com/axios/axios), [flatted](https://github.com/WebReflection/flatted) and [tmp](https://github.com/raszi/node-tmp).


Updates `js-yaml` from 5.1.0 to 5.2.1
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@5.1.0...5.2.1)

Updates `axios` from 1.16.0 to 1.18.1
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md)
- [Commits](axios/axios@v1.16.0...v1.18.1)

Updates `flatted` from 3.3.3 to 3.4.2
- [Commits](WebReflection/flatted@v3.3.3...v3.4.2)

Updates `tmp` from 0.2.5 to 0.2.7
- [Changelog](https://github.com/raszi/node-tmp/blob/master/CHANGELOG.md)
- [Commits](raszi/node-tmp@v0.2.5...v0.2.7)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 5.2.1
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: axios
  dependency-version: 1.18.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: flatted
  dependency-version: 3.4.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: tmp
  dependency-version: 0.2.7
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
…_yarn-486176253e

Bump the npm_and_yarn group across 1 directory with 4 updates
Bumps the npm_and_yarn group with 1 update in the / directory: [body-parser](https://github.com/expressjs/body-parser).


Updates `body-parser` from 2.2.1 to 2.3.0
- [Release notes](https://github.com/expressjs/body-parser/releases)
- [Changelog](https://github.com/expressjs/body-parser/blob/master/HISTORY.md)
- [Commits](expressjs/body-parser@v2.2.1...v2.3.0)

---
updated-dependencies:
- dependency-name: body-parser
  dependency-version: 2.3.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
…_yarn-c3809050de

Bump body-parser from 2.2.1 to 2.3.0 in the npm_and_yarn group across 1 directory
Bumps the npm_and_yarn group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [next](https://github.com/vercel/next.js) | `16.2.6` | `16.2.11` |
| [sharp](https://github.com/lovell/sharp) | `0.33.5` | `0.35.0` |
| [fast-uri](https://github.com/fastify/fast-uri) | `3.1.2` | `3.1.4` |
| [immutable](https://github.com/immutable-js/immutable-js) | `5.1.5` | `5.1.9` |
| [linkify-it](https://github.com/markdown-it/linkify-it) | `5.0.1` | `5.0.2` |



Updates `next` from 16.2.6 to 16.2.11
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.2.6...v16.2.11)

Updates `sharp` from 0.33.5 to 0.35.0
- [Release notes](https://github.com/lovell/sharp/releases)
- [Commits](lovell/sharp@v0.33.5...v0.35.0)

Updates `fast-uri` from 3.1.2 to 3.1.4
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](fastify/fast-uri@v3.1.2...v3.1.4)

Updates `immutable` from 5.1.5 to 5.1.9
- [Release notes](https://github.com/immutable-js/immutable-js/releases)
- [Changelog](https://github.com/immutable-js/immutable-js/blob/main/CHANGELOG.md)
- [Commits](immutable-js/immutable-js@v5.1.5...v5.1.9)

Updates `linkify-it` from 5.0.1 to 5.0.2
- [Changelog](https://github.com/markdown-it/linkify-it/blob/master/CHANGELOG.md)
- [Commits](markdown-it/linkify-it@5.0.1...5.0.2)

---
updated-dependencies:
- dependency-name: next
  dependency-version: 16.2.11
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: sharp
  dependency-version: 0.35.0
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: fast-uri
  dependency-version: 3.1.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: immutable
  dependency-version: 5.1.9
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: linkify-it
  dependency-version: 5.0.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
…_yarn-cfa85fc350

Bump the npm_and_yarn group across 1 directory with 5 updates
…rifying-or-approving-a-domain-for-your-organization.md
@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jul 23, 2026

@clauderiks clauderiks left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

auren-os

@github-actions

github-actions Bot commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

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.

@github-actions

Copy link
Copy Markdown
Contributor

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

  • .github/FUNDING.yml
  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/custom.md
  • .github/ISSUE_TEMPLATE/feature_request.md
  • .github/workflows/Thingking
  • .github/workflows/nextjs.yml
  • package-lock.json
  • package.json

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/how-tos/security-for-github-actions/security-hardening-your-deployments/**

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

@clauderiks

This comment was marked as spam.

@github-actions

Copy link
Copy Markdown
Contributor

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

  • .github/FUNDING.yml
  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/custom.md
  • .github/ISSUE_TEMPLATE/feature_request.md
  • .github/workflows/Thingking
  • .github/workflows/nextjs.yml
  • package-lock.json
  • package.json

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/how-tos/security-for-github-actions/security-hardening-your-deployments/**

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

Signed-off-by: Clriks <241179063+clauderiks@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

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

  • .github/FUNDING.yml
  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/custom.md
  • .github/ISSUE_TEMPLATE/feature_request.md
  • .github/workflows/Thingking
  • .github/workflows/nextjs.yml
  • package-lock.json
  • package.json

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/how-tos/security-for-github-actions/security-hardening-your-deployments/**

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

# Sandboxcode Docs <!-- omit in toc -->

Welcome to sandboxcode Docs! sandboxcode’s documentation is open source, meaning anyone from inside or outside the company can contribute. For full contributing guidelines, visit our [contributing guide](https://docs.github.com/en/contributing).


## Quick links by contributor type

* **Hubbers (GitHub employees):** See [CONTRIBUTING.md](https://github.com/github/docs-content/blob/main/CONTRIBUTING.md) in the `docs-content` repository for GitHub-specific processes.

* **Open source contributors:** See [CONTRIBUTING.md](https://github.com/github/docs/blob/main/.github/CONTRIBUTING.md) in the `docs` repository for a quick-start summary.

## How we sync changes across Docs repositories

There are two GitHub Docs repositories: 

- **`github/docs`** (public): Open to external contributions

- **`github/docs-internal`** (private): For GitHub employee contributions. 

The two repositories sync frequently. Content changes in one are reflected in the other.  Hubbers might prefer to post in `docs` when working with a customer, but `docs` has limitations on the types of contributions it accepts to safeguard the site and our workflows. Internal contributions should usually go to `docs-internal`.

**Important:** The `docs` repository accepts contributions to content files (`.md` files in `/content` and select `/data` sections like reusables only). Infrastructure files, workflows, and site-building code are not open for external modification.

## New to contributing

Here are some resources to help you get started with open source contributions:

* [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
* [Set up Git](https://docs.github.com/en/get-started/git-basics/set-up-git)
* [GitHub flow](https://docs.github.com/en/get-started/using-github/github-flow)
* [Collaborating with pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests)

## License

This project is dual-licensed under:

* **Creative Commons Attribution 4.0** - for documentation and content in the assets, content, and data folders (see [LICENSE](LICENSE))
* **MIT License** - for code (see [LICENSE-CODE](LICENSE-CODE))


Signed-off-by: Clriks <241179063+clauderiks@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

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

  • .github/FUNDING.yml
  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/custom.md
  • .github/ISSUE_TEMPLATE/feature_request.md
  • .github/workflows/Thingking
  • .github/workflows/nextjs.yml
  • package-lock.json
  • package.json

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/how-tos/security-for-github-actions/security-hardening-your-deployments/**

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants