Contributing tab on rendered Readme.md has broken links to two images, under .github/Images, but previews ok in .github/Contributing.md

Open Beginner friendly
#28,256 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Soumilgit is already working on this.

Since Oct 25, 2026.

  • #28257 by @Soumilgit — open

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
github, markdown
Domain
documentation

Research direction

Start by comparing the two image links in the rendered README's Contributing tab with their working previews in .github/Contributing.md. Check the repository's Markdown link behavior and the linked GitHub discussion before choosing the paths. Done when both images render and their links resolve from the repository root.

Written by the indexing model from the issue text.

Description

Issue-Enhancement Needs-Triage
Summary of the new feature / enhancement

The two links are to Images/Codespaces.png (renders as "alt text") and Images/GitHub-PR.png (renders as the picture filename), which give a 404 when clicked from the PowerShell/PowerShell root directory, but show up ok when opening .github/Contributing.md
As this was a documentation issue, but for a file in this repository, I looked for any discussion in MicrosoftDocs/PowerShell-Docs - but not finding any, I opened this issue.

Proposed technical implementation details (optional)

Should the two links be changed to absolute paths to /.github/Images , like suggested in this recent GitHub discussion (https://github.com/orgs/community/discussions/200300)?

Dominant language
C#
Stars
56.1k
Forks
8.5k
Avg merge
12h 33m
Merged PRs (30d)
73

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PowerShell

All issues in PowerShell/PowerShell

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.