feat: extract multiple repos for given owner/orgs by running api command#1278
Merged
sbillinge merged 3 commits intoregro:mainfrom Dec 29, 2025
Merged
feat: extract multiple repos for given owner/orgs by running api command#1278sbillinge merged 3 commits intoregro:mainfrom
sbillinge merged 3 commits intoregro:mainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1278 +/- ##
==========================================
+ Coverage 79.64% 79.86% +0.22%
==========================================
Files 17 17
Lines 1366 1381 +15
==========================================
+ Hits 1088 1103 +15
Misses 278 278 🚀 New features to boost your workflow:
|
Contributor
|
Thanks @stevenhua0320. Please can we move the yaml to ruamel and then I can merge |
Contributor
|
thanks @stevenhua0320 |
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.
@sbillinge Ready for review, note that for
releasesfield I did not test as for my own repo I do not have any release. We might test this and if there is any formatting issue insoftware.ymlgenerated, I could make edits on that. The other fields I have tested locally and it should be right.To use this, we first have the Github personal access token export on local. Then use the command
regolith gh-extractor <owner> --allto extract all repos orregolith gh-extractor <owner> <package-name>for individual package. Then it would generate thesoftware.ymlfor the packages. After that we use the originalregolith build releaselistcommand to build the releaselist report.