fix(code-security): repair validity checks anchor - #46078
Merged
subatoi merged 1 commit intoSep 25, 2026
Merged
Conversation
github-actions
Bot
added
the
triage
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 linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
*Subject: GitHub Copilot Access Restricted Despite Verified Teacher Status*
Hello GitHub Support,
I am a teacher and an education-sector professional, using my
university/educational email with my GitHub account.
My GitHub Copilot access is being stopped until the beginning of the next
month. I would like to understand why this is happening and whether my
educational/teacher eligibility is correctly recognized.
I actively use GitHub for large repositories, projects, and multiple
development integrations, so this restriction is significantly affecting my
work.
Could you please review my account and clarify:
- Is my teacher/education status correctly verified?
- What specific Copilot limit has my account reached?
- Why is access blocked until the beginning of next month?
- Am I receiving all Copilot benefits available to verified teachers?
- Is there anything I need to do to restore or maintain my Copilot
access?
I would appreciate a manual review of my account and a clear explanation of
the restriction.
Thank you.
في الجمعة، ٢٥ سبتمبر ٢٠٢٦، ٢:٣٤ م github-actions[bot] <
***@***.***> كتب:
… *github-actions[bot]* left a comment (github/docs#46078)
<#46078 (comment)>
How to review these changes 👓
Thank you for your contribution. To review these changes, choose one of
the following options:
- Spin up a codespace
<https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace>
- Set up a local development environment
<https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment#setting-up-your-local-environment>
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.
The table shows the files in the content directory that were changed in
this pull request. This helps you review your changes on a staging server.
Changes to the data directory are not included in this table.
*Source* *Review* *Production* *What Changed*
code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning.md
<https://github.com/github/docs/blob/6e46ae3425fa2e8fb5a789aca4ed84bd2b85de56/content%2Fcode-security%2Fhow-tos%2Fsecure-at-scale%2Fconfigure-enterprise-security%2Fconfigure-specific-tools%2Fconfigure-secret-scanning.md>
ghes@ 3.22
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.21
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.20
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.19
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.18
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.17
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
ghes@ 3.22
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.21
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.20
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.19
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.18
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
3.17
***@***.***/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning>
Key: *fpt*: Free, Pro, Team; *ghec*: GitHub Enterprise Cloud; *ghes*:
GitHub Enterprise Server
🤖 This comment is automatically generated
<https://github.com/github/docs/blob/75ea7dd097a5564f27364a5b70eaa1979106eabd/.github/workflows/review-comment.yml>
.
—
Reply to this email directly, view it on GitHub
<#46078?email_source=notifications&email_token=BJEV2LC4UL7GIBT3G46DC5D5QZJ3JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOBTGE3DQNRQGE42M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-5831686019>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BJEV2LHITH4JJJTYEUQDHPT5QZJ3JAVCNFSNUABFKJSXA33TNF2G64TZHMYTQOJWGIYTMMBXHNEXG43VMU5TKNJYGIZDAMBUHAYKC5QC>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
subatoi
approved these changes
Sep 25, 2026
subatoi
left a comment
subatoi
left a comment
Contributor
There was a problem hiding this comment.
Thanks @aniruddhaadak80—I'll get this merged now
Contributor
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
|
Vào Thứ 6, 25 thg 9, 2026 lúc 20:37 subatoi ***@***.***> đã
viết:
… Merged #46078 <#46078> into main.
—
Reply to this email directly, view it on GitHub
<#46078?email_source=notifications&email_token=BVO7RSINR5UDB7GJHELCUB35QZYH3A5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMJYGM4DSMJRGM3TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#event-31838911371>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BVO7RSIDXE6K3CQ5LL67Q6L5QZYH3AVCNFSNUABFKJSXA33TNF2G64TZHMYTQOJWGIYTMMBXHNEXG43VMU5TKNJYGIZDAMBUHAYKC5QC>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BVO7RSPM4K476SS4EZLYA5T5QZYH3A5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMJYGM4DSMJRGM3TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG>
and Android
<https://github.com/notifications/mobile/android/BVO7RSOP3NJ2HQYGQB6DGA35QZYH3A5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMJYGM4DSMJRGM3TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
Download it today!
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why:
Closes #46076
The enterprise secret scanning setup guide linked to
#about-validity-checks, but the target article has no such heading or rendered ID. The existing target heading isEnabling validity checks, so readers following the link were sent to a nonexistent fragment.What's being changed (if available, include any code snippets, screenshots, or gifs):
#enabling-validity-checks.Validation completed with Node.js v24.19.0:
npm run build— passed.npm run lint-content -- --paths content/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning.md— passed with no errors.npm test -- --no-file-parallelism --maxWorkers=1 src/content-render/tests/render-changed-and-deleted-files.tswithCHANGED_FILESset to the edited article — 2 tests passed.npm run check-links-pr -- --files content/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning.md— 6 links checked; no broken links. The checker reported three unrelated pre-existing redirects elsewhere in the same article.npm run tsc— passed.git diff --check— passed.Check off the following: