docs: fix PipeCD docs package metadata links#6799
Open
ObaidAbdullah16 wants to merge 1 commit into
Open
Conversation
Signed-off-by: ObaidAbdullah16 <obaidabdullah1610@gmail.com>
ObaidAbdullah16
requested review from
Warashi,
eeshaanSA,
ffjlabo and
khanhtc1202
ObaidAbdullah16
force-pushed
the
docs-fix-package-metadata
branch
from
5f5913e to
7de0edf
Compare
Author
|
@khanhtc1202 @Warashi @ffjlabo @eeshaanSA, Please look when you have time for review. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
Updates
docs/package.jsonmetadata (repository URL, issues URL, and homepage) so it points topipe-cd/pipecdinstead ofgoogle/docsy-example.Why we need it:
The docs site package metadata is currently misleading and directs contributors to the wrong repository/issue tracker. Updating it makes the docs tooling metadata accurate and avoids confusion.
Does this PR introduce a user-facing change?:
No