You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
The PR form in markdown that we have to fill contains a dead link. To be honest, I am not really sure whether this is the right channel to report this. Forgive if it is not.
Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:
Steps to Reproduce
Can this be reproduced in the Sample App? (Either in a sample as-is or with new XAML pasted in the editor.) If so, please provide custom XAML or steps to reproduce. If not, let us know why it can't be reproduced (e.g. more complex setup, environment, dependencies, etc...)
FYI @Nirmal4G this is also why renaming files can be problematic as they're case-sensitive for GitHub urls (readme.md != ReadMe.md). Not sure what other places we link to any of the files you've renamed. Can you revert your file name changes please before we diverge or find other cases where we may have issues? Thanks!
Original link was also broken. I've checked this too when creating my recent PRs. It was on my todo list. I wanted to check whether we have direct link references to readme.md in the wild, either to revert the rename or simply adjust our PR form link.
Seems, there are no direct references to our link outside our repo. Hence, it's safe to just update our links to reflect that. I have also updated my recent PR description to working link to confirm it.
Activity
michael-hawker commentedon Jul 28, 2021
Thanks @thiago-cs looks like the link should be https://github.com/CommunityToolkit/WindowsCommunityToolkit/blob/main/ReadMe.md#supported (not sure how the original link could have worked in the past though, so probably just an oversight). The PR template is here. Hmm, it uses relative links, so this may be a quirk of GitHub depending on where it's looking... We may need to put a full URL in there.
FYI @Nirmal4G this is also why renaming files can be problematic as they're case-sensitive for GitHub urls (readme.md != ReadMe.md). Not sure what other places we link to any of the files you've renamed. Can you revert your file name changes please before we diverge or find other cases where we may have issues? Thanks!
Nirmal4G commentedon Jul 29, 2021
Original link was also broken. I've checked this too when creating my recent PRs. It was on my todo list. I wanted to check whether we have direct link references to
readme.mdin the wild, either to revert the rename or simply adjust our PR form link.Seems, there are no direct references to our link outside our repo. Hence, it's safe to just update our links to reflect that. I have also updated my recent PR description to working link to confirm it.
See that the link https://github.com/CommunityToolkit/WindowsCommunityToolkit/ReadMe.md#supported also doesn't work.
But, the link https://github.com/CommunityToolkit/WindowsCommunityToolkit#supported works. If we want a relative link, then the link
../#supportedalso works.I've updated my markdown PR with this patch.