NO-ISSUE: fix sync main capture uncommitted changes step #52
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
ricardozanini
approved these changes
Jan 10, 2025
rgdoliveira
approved these changes
Jan 10, 2025
fantonangeli
deleted the
NO-ISSUE-fix-sync-main-capture-uncommitted-changes-step
branch
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.
This PR fixes a check related to the
git status --porcelainoutput.This fixes also an error:
pull request create failed: GraphQL: Body is too long (maximum is 65536 characters)which happens when
SYNC_CHANGESis too big and truncate it with...I tested the CI running on my for with:
kubesmarts/kie-tools:mainbranch with last commit on 11-12-2024:[2025-01-10:165831] - 🤖 Automated PR: Sync main with upstream fantonangeli/kie-tools#35
kubesmarts/kie-tools:mainbranch[2025-01-10:171104] - 🤖 Automated PR: Sync main with upstream fantonangeli/kie-tools#36