-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-existent repo callout and repo-list output for which repo being processed #45
Comments
This comment was marked as spam.
This comment was marked as spam.
/github/migration/stats$ cat ./repo-list.txt /github/migration/stats$ gh repo-stats --org myorg --repo-list ./repo-list.txt ###################################################### User provided a repo list file. Mapping contents...Getting repositories for org: myorg ###################################################### Results file:[myorg-all_repos-202305031643.csv] /github/migration/stats$ cat ./myorg-all_repos-202305031643.csv |
Related to mona-actions#45 Add repository processing status and handle non-existent repositories in `gh-repo-stats`. * Add a new column `status` to the .csv file to indicate the status of each repository ('completed', 'not found', 'error'). * Update the `ParseRepoData` function to include the `status` parameter and write it to the .csv file. * Display the currently processed repository in the output when using `--repo-list`. * Identify non-existent repositories in the `--repo-list` file and mark them as 'not found' in the output and .csv file. * Update the header of the .csv file to include the new `status` column. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/mona-actions/gh-repo-stats/issues/45?shareId=XXXX-XXXX-XXXX-XXXX).
✨✨ Here's an AI-assisted sketch of how you might approach this issue saved by @LuCaSiNo40 using Copilot Workspace v0.27 |
A couple minor improvement suggestions. Great tooling btw! 🏆
When using --repo-list, it would be nice to know which repository is being processed by showing that in the output. Currently there's only a rate limit callout with wording stating "getting repositories for org". For repos with thousands of records it can take a very long time to run, so knowing which repo it's on is helpful. Note that running against the entire org, without --repo-list, does show the repo being processed, so it seems to be limited to --repo-list only. See output below for example.
When using --repo-list, any repos included that don't exist are not identified in the output as an issue. They are not included in the .csv either, which I guess is expected, but if you have a large list you're left wondering why the count of the results is off from the number of repos in the repo-list file.
Possible Solutions:
status
, or something like that, in the .csv and include status of 'completed', 'not found', 'error'. If not found, then all stats could be 0 with the status 'not found'. If some of the stats were retrieved but not all. due to API limit or some other issue, having status of 'error' would let us know we're missing data.Sample of testing around the issues mentioned. Repo name and org were swapped to generic in the output below.
The text was updated successfully, but these errors were encountered: