chore(internal/postprocessor): process new mods #9567
Merged
Conversation
This file contains 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
quartzmo
approved these changes
Mar 12, 2024
|
Verified locally that the new |
gcf-merge-on-green bot
pushed a commit
that referenced
this pull request
Mar 13, 2024
To capture fix in #9567
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.
When initializing a new
go.modfile, add it to the list ofmodulesthat would otherwise be derived from the OwlBot PR body (that is actually processed by the post processor!) so that it is processed (e.g. tidied) with the rest of the modules changed in the PR.I explicitly didn't change the logic to tidy modules based on which modules were changed b.c I don't want to make too big a change without having a clear idea of the impact. In the meantime, this fix will keep things ticking over with a little bit less manual toil.
Fixes #9560