Skip to content

Conversation

@jonasbn
Copy link

@jonasbn jonasbn commented Oct 31, 2025

Why:

Closes: #41072

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

As outlined in the issue, the links pointing to:

  • https://github.com/github/awesome-copilot/blob/main/README.instructions.md are resulting in 404

Example page:

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.
Copilot AI review requested due to automatic review settings October 31, 2025 07:20
@welcome
Copy link

welcome bot commented Oct 31, 2025

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 Oct 31, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 31, 2025

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.

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
copilot/tutorials/customization-library/custom-instructions/accessibility-auditor.md fpt
ghec
fpt
ghec
from reusable
copilot/tutorials/customization-library/custom-instructions/code-reviewer.md fpt
ghec
fpt
ghec
from reusable
copilot/tutorials/customization-library/custom-instructions/concept-explainer.md fpt
ghec
fpt
ghec
from reusable
copilot/tutorials/customization-library/custom-instructions/debugging-tutor.md fpt
ghec
fpt
ghec
from reusable
copilot/tutorials/customization-library/custom-instructions/github-actions-helper.md fpt
ghec
fpt
ghec
from reusable
copilot/tutorials/customization-library/custom-instructions/issue-manager.md fpt
ghec
fpt
ghec
from reusable
copilot/tutorials/customization-library/custom-instructions/pull-request-assistant.md fpt
ghec
fpt
ghec
from reusable
copilot/tutorials/customization-library/custom-instructions/your-first-custom-instructions.md fpt
ghec
fpt
ghec
from reusable

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the URL path for the "Awesome GitHub Copilot Customizations" repository links across reusable content files. The links previously pointed to README.instructions.md but are now corrected to point to README.md.

Key changes:

  • Updated the repository link URL from README.instructions.md to README.md in two reusable content files

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
data/reusables/copilot/customization-examples-note.md Corrected the URL path in the note about community-contributed examples
data/reusables/copilot/custom-instructions-further-reading.md Corrected the URL path in the further reading section

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

jerod0668-create referenced this pull request Oct 31, 2025
Co-authored-by: Jules Porter <jules-p@users.noreply.github.com>
@Sharra-writes
Copy link
Contributor

@jonasbn We just merged a PR updating the second link earlier today (which is why there's a "this branch has conflicts that must be resolved" warning right now). If you could get rid of that change, I will happily accept and merge the other one!

@jonasbn
Copy link
Author

jonasbn commented Nov 1, 2025

Hi @Sharra-writes

I have accepted and merged the incoming change as per the merge conflict.

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

2 participants