Skip to content

chore(docs): improve release flow automation scripts robustness#12

Merged
assagman merged 1 commit intomainfrom
chore/release-flow-error-handling
Jan 25, 2026
Merged

chore(docs): improve release flow automation scripts robustness#12
assagman merged 1 commit intomainfrom
chore/release-flow-error-handling

Conversation

@assagman
Copy link
Owner

Summary

This PR improves the robustness of the release flow scripts in docs/RELEASE-FLOW.md by:

  • Adding error checks when looking for the release PR.
  • Implementing a more resilient waiting loop for GitHub Actions workflows that handles failures, cancellations, and skips instead of waiting indefinitely.

Signed-off-by: assagman <ahmetsercansagman@gmail.com>
Copilot AI review requested due to automatic review settings January 25, 2026 18:41
@gemini-code-assist
Copy link

Summary of Changes

Hello @assagman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the reliability of the release automation scripts by introducing robust error handling for critical steps. It ensures that the scripts can gracefully manage scenarios where expected resources, like an open release PR, are not found, and provides more intelligent waiting for GitHub Actions workflows, preventing indefinite hangs on non-successful outcomes.

Highlights

  • Release PR Lookup Robustness: Added error checks to ensure an open release PR is found before attempting to merge it, preventing script failures if no such PR exists.
  • GitHub Actions Workflow Waiting: Enhanced the waiting mechanism for GitHub Actions workflows to explicitly handle 'failure', 'cancelled', and 'skipped' conclusions, exiting the script gracefully instead of waiting indefinitely for a 'success' state.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@codecov
Copy link

codecov bot commented Jan 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@assagman assagman merged commit 718a81f into main Jan 25, 2026
6 checks passed
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request improves the robustness of the release automation scripts by adding necessary checks for the existence of a release PR and by implementing more resilient waiting loops for GitHub Actions workflows. The changes are solid and correctly address potential failure points. I have a couple of suggestions to further simplify the workflow waiting logic by using the gh run watch command, which is designed for this purpose and can make the script more concise and readable.

@assagman assagman deleted the chore/release-flow-error-handling branch January 25, 2026 18:42
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Improves the release-flow documentation scripts to fail fast when expected artifacts (release PR, workflow runs) are missing or unsuccessful, avoiding indefinite waits.

Changes:

  • Add a guard clause to error out when no open release PR is found before attempting merge.
  • Replace “wait until success” loops with polling that exits on non-success workflow conclusions (failure/cancelled/skipped).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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