Adding repodiving.md to inbound section of OSPO-guide - #134
Merged
Conversation
decause-gov
approved these changes
Jul 28, 2026
decause-gov
left a comment
Contributor
There was a problem hiding this comment.
Great work here @isaac-rtc
If the documentation on repodive-tools itself does not reflect these changes, we should also update the docs over there to include this improved documentation. Nice job!
Contributor
Author
Thanks @decause-gov ! I'll merge this and then work on updating docs on the repodice-tools itself, I'll add you as reviewer once done! |
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.
Problem
The OSPO Guide did not contain onboarding documentation for the repodive-tools toolkit, requiring users to rely on the standalone repository README to understand the available scripts, required dependencies, and usage workflows. The existing documentation also lacked additional context around how the tools fit together, their prerequisites, and supporting repository analysis techniques.
Solution
repodive-toolsrepository into a structured onboarding guide.git,curl,jq,scc, andgource) with installation links and brief explanations of each tool.Result
Contributors now have a centralized onboarding resource within the OSPO Guide that explains the purpose of each repodive script, required setup, supporting dependencies, and common repository analysis workflows without needing to rely solely on the
repodive-toolsREADME.Test Plan