fix(docs): "Edit this page" URLs to correctly point to GitHub repository structure #5289
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
ntheanh201
requested review from
nghialv,
khanhtc1202,
kentakozuka,
ffjlabo,
t-kikuc and
Warashi
as code owners
|
@ntheanh201 cf. https://github.com/pipe-cd/pipecd/pull/5289/checks?check_run_id=31926903751 |
t-kikuc
reviewed
Oct 23, 2024
Signed-off-by: The Anh Nguyen <[email protected]>
Signed-off-by: The Anh Nguyen <[email protected]>
Signed-off-by: The Anh Nguyen <[email protected]>
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 this PR does:
This PR fixes the "Edit this page" URLs in the documentation pages to correctly point to the appropriate locations in the GitHub repository structure.
Why we need it:
The current "Edit this page" URLs are incorrect, pointing to a wrong path in the repository (missing .md extension).
Which issue(s) this PR fixes:
Fixes #5287
Does this PR introduce a user-facing change?: