Fix link to CI and Workflow Integration guide#607
Closed
aryan105825 wants to merge 1 commit into
Closed
Conversation
Collaborator
|
@aryan105825 Thank you for your contributions, but this was already addressed in #606. |
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
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.
Summary
Fixes a broken documentation link in the README that pointed to a non-existent page (
/docs/ci-integration). Updated it to the correct URL (/docs/workflow-integration).Why this change
The README linked to
https://owasp.org/cve-lite-cli/docs/ci-integrationwhich returns a 404. The correct and existing page ishttps://owasp.org/cve-lite-cli/docs/workflow-integration. This was reported in issue #605.What changed
ci-integrationdocs link in README toworkflow-integrationValidation
Verified that the updated URL (
https://owasp.org/cve-lite-cli/docs/workflow-integration) resolves correctly. No code changes were made, so no build or test changes are required.User-facing impact
Does this change:
Notes
This is a docs-only fix. Closes #605.