Skip to content

chore: change to post submit and create an issue on failure#13309

Closed
sofisl wants to merge 3 commits into
mainfrom
changePreToPost
Closed

chore: change to post submit and create an issue on failure#13309
sofisl wants to merge 3 commits into
mainfrom
changePreToPost

Conversation

@sofisl

@sofisl sofisl commented May 29, 2026

Copy link
Copy Markdown
Contributor

Converts the presubmit to a postsubmit check to not delay PRs. Creates issues if necessary. Per googleapis/librarian#5240 (comment).

Fixes 5240

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@sofisl sofisl marked this pull request as ready for review May 29, 2026 19:51
@sofisl sofisl requested review from a team as code owners May 29, 2026 19:51
@sofisl sofisl enabled auto-merge (squash) June 1, 2026 20:46
@sofisl sofisl disabled auto-merge June 1, 2026 20:46

@zhumin8 zhumin8 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Change LGTM. However, I don't think we are ready to merge this now:

@sofisl sofisl enabled auto-merge (squash) June 1, 2026 20:46
@sofisl sofisl disabled auto-merge June 1, 2026 20:47
@sofisl

sofisl commented Jun 4, 2026

Copy link
Copy Markdown
Contributor Author

From Min:

I would pause and merge this in toward the end of next week (when we turn done hermetic build workflow and librarian.yaml is the source of truth).

- name: Check for generated code changes
run: |
git diff --exit-code
- name: Create issue if previous step fails

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Considering current generate all runs for 1 hour +, If one PR is merged causing generation diff, it's likely subsequent PRs are merged. This will create repeating issues. I think we want to combine them to not over-pollute the issue board.
In fact, I believe we can reuse this action from librarian that already does exactly this. https://github.com/googleapis/librarian/tree/main/.github/actions/create-issue-on-failure

@zhumin8

zhumin8 commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

closing in favor of #13422

@zhumin8 zhumin8 closed this Jun 10, 2026
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.

google-cloud-java: create a workflow to run librarian generate -all and create issue on failure

3 participants