fix(ci): remove unnecessary rebase step causing dirty tree error in release workflow#14
Merged
Conversation
Co-authored-by: pckimlong <78638472+pckimlong@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Issue with dirty tree of that CI
fix(ci): remove unnecessary rebase step causing dirty tree error in release workflow
Sep 21, 2025
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a CI workflow issue where the release workflow was failing due to a "dirty tree" error caused by an unnecessary rebase step. The workflow was attempting to rebase after committing version bump changes, which created conflicts since the workflow already runs on the main branch.
- Removed the problematic "Rebase onto latest main" step from the release workflow
- Simplified the release flow to avoid git conflicts while maintaining all functionality
This file contains hidden or 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
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.
The release workflow was failing with a "dirty tree" error during the rebase step. The error occurred because:
bump_version.pyscript modifiespubspec.yamlandCHANGELOG.mdorigin/main, which conflicts with the committed changesRoot Cause: The rebase step was unnecessary since the release workflow only runs on pushes to the main branch. There's no need to rebase when we're already working on the target branch.
Solution: Removed the "Rebase onto latest main" step from
.github/workflows/release.yml. The workflow now follows a cleaner, more logical flow:This eliminates the source of the conflict while maintaining all the release functionality.
Fixes #13.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://storage.googleapis.com/flutter_infra_release/flutter/c29809135135e262a912cf583b2c90deb9ded610/dart-sdk-linux-x64.zipcurl --retry 3 --continue-at - --location --output /tmp/flutter/bin/cache/dart-sdk-linux-x64.zip REDACTED(http block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.