[6582] fix: Broken Link in Issue Template Documentation #6615
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tengqm hope you're now satisfied. |
|
lgtm. |
jerryshao
approved these changes
Mar 6, 2025
|
@jerryshao updated branch can u run the workflows. |
|
@Brijeshthummar02 it is unnecessary to update the branch if there's no conflict, the updating will rerun all the CI tasks, which is time-consuming. GitHub will rebase your PR when merged. |
|
Oh got it, i was not aware about it. |
justinmclean
approved these changes
Mar 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR fixes a broken link in the issue template documentation. The updated link correctly directs users to the structured issue template documentation.
Why are the changes needed?
The link should direct users to the correct documentation on structured issue templates.
fix #6582 , closes #6583
Does this PR introduce any user-facing change?
No. This is a documentation fix and does not impact any user-facing functionality.
How was this patch tested?
Since this is a documentation update, no functional tests were required. However, the updated link was manually verified to ensure it directs users to the correct documentation.