Skip to content
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

feat: Allow a container-clean api-path of "none" #14012

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

jskeet
Copy link
Collaborator

@jskeet jskeet commented Dec 16, 2024

When provided "none", the container should clean just non-API-specific files.

(This is needed for the configure CLI command.)

When provided "none", the container should clean just
non-API-specific files.
@@ -25,6 +25,7 @@ namespace Google.Cloud.Tools.ReleaseManager.ContainerCommands;
/// - repo-root: path to the root of the clone
/// - api-path: path to the API to clean generated files from, e.g. google/cloud/functions/v2
/// This is optional; when omitted, all configured APIs are cleaned.
/// The special value of "none" means "clean non-API-specific files only".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For later: Wondering if api-path should be required, with a couple of magic values "none" and "all"?

Alternative, with hide that from the surface and have three commands: clean-api, clean-all, clean-common?

Definetely something for another PR though.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You read my mind (first option): googleapis/generator#67

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice :)

@jskeet jskeet merged commit 1402395 into googleapis:main Dec 16, 2024
9 checks passed
@jskeet jskeet deleted the clean-none branch December 16, 2024 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants