add configuration file support #151
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| config_repositories: list[str] | None = None | ||
| if "repositories" in config_data: | ||
| try: | ||
| config_repositories = _parse_repositories( | ||
| config_data.get("repositories"), | ||
| ) | ||
| except ConfigError as exc: | ||
| print(exc) # noqa: T201 | ||
| sys.exit(1) | ||
|
|
||
| org_name = args.org if args.org is not None else config_data.get("org") | ||
| if not org_name and not config_repositories: | ||
| print("Error: Provide an organization or repositories to analyze") # noqa: T201 | ||
| sys.exit(1) |
There was a problem hiding this comment.
The new config validation requires either an organization or a repositories list to be supplied. This check runs before the CLI looks at --clear-cache, --clear-expired-cache, or --cache-stats, so commands like review-tally --clear-cache now exit with "Error: Provide an organization or repositories to analyze" even though cache management doesn’t need repository context. Previously these operations worked without an org, and the early return in main() still bypasses repository fetching. Consider skipping this validation when any cache-maintenance flag is set so users can manage the cache without supplying irrelevant org information.
Useful? React with 👍 / 👎.
ghinks
changed the title
|
closing PR due to merge conflicts. |
Summary
Testing
https://chatgpt.com/codex/tasks/task_e_68fd08f326d8833088bbb235c9cd1115