Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Few broken links in markdown files #49490

Closed
Youssef1313 opened this issue Mar 11, 2021 · 2 comments
Closed

Few broken links in markdown files #49490

Youssef1313 opened this issue Mar 11, 2021 · 2 comments
Labels
area-Meta documentation Documentation bug or enhancement, does not impact product or test code good first issue Issue should be easy to implement, good for first-time contributors help wanted [up-for-grabs] Good issue for external contributors needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration

Comments

@Youssef1313
Copy link
Member

See https://github.com/Youssef1313/runtime/actions/runs/643550434

cc: @danmoseley Per previous discussion on having a GitHub Action that verifies links. There doesn't seem to be a markdownlint rule for it, so I made my own GH Action. Above is the results from the run. Let me know if it contains any false positives.

I don't know if you'll want to have the repo use this GH Action. You can either only fix the links, or both fix them and add the workflow.
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Mar 11, 2021
@joperezr joperezr added documentation Documentation bug or enhancement, does not impact product or test code help wanted [up-for-grabs] Good issue for external contributors good first issue Issue should be easy to implement, good for first-time contributors and removed untriaged New issue has not been triaged by the area owner labels Mar 31, 2021
@miraantolovich miraantolovich mentioned this issue Apr 2, 2021
Merged
@SimonCropp
Copy link
Contributor

#50653 is merged, so this should be closed?

@ghost ghost added the needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration label May 24, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jun 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-Meta documentation Documentation bug or enhancement, does not impact product or test code good first issue Issue should be easy to implement, good for first-time contributors help wanted [up-for-grabs] Good issue for external contributors needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration
Projects
No open projects
Triage POD for Reflection, META, etc.
Status: Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@SimonCropp @jeffschwMSFT @joperezr @Youssef1313