Contributing tab on rendered Readme.md has broken links to two images, under .github/Images, but previews ok in .github/Contributing.md
Maintainers usually reply within 1 day
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
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
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PowerShell/PowerShell
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PowerShell/PowerShell#28432 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Needs-Investigation WG-Engine WG-NeedsReview
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PowerShell/PowerShell#28283 · 1 comment ·
Maintainers usually reply within 1 day
-
Issue-Enhancement Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
PowerShell/PowerShell#28138 · 1 reaction ·
Maintainers usually reply within 1 day
-
Add support for WebRequestMethod QUERYPossibly taken @soroshsabz claimed this 52 days ago. OpenIssue-Enhancement Up-for-Grabs WG-Cmdlets WG-Reviewed
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PowerShell/PowerShell#28061 · 4 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
PowerShell/PowerShell#28037 ·
Maintainers usually reply within 1 day
All issues in PowerShell/PowerShell
Similar issues
-
area-templates triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/aspire#22356 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/aspire.dev#2184 ·
Maintainers usually reply within 2 days
-
area-controls-refreshview platform/ios s/triaged
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dotnet/maui#40314 · 1 reaction ·
Maintainers usually reply within 1 day
-
Needs: Triage (Functions) v5 v5-preview5
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Azure/azure-functions-core-tools#5918 ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elsa-workflows/elsa-foundation#4712 · 1 comment ·
Maintainers usually reply within 1 day