Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjustment to merge-asset-tags #7556

Merged
merged 1 commit into from
Jan 22, 2024
Merged

Adjustment to merge-asset-tags #7556

merged 1 commit into from
Jan 22, 2024

Conversation

scbedd
Copy link
Member

@scbedd scbedd commented Jan 20, 2024

Turns out, when a changeset includes the same changes, but a different parent commit, cherry-pick kinda flips out with a

conflicts present

then shows no modified files in git status.

Base commit: Automatic asset update from test-proxy. · Azure/azure-sdk-assets@c56e4d5 (github.com)
Mergee commit: Automatic asset update from test-proxy. · Azure/azure-sdk-assets@aa77628 (github.com)

Notice that the actual contents of the commits are the same, but the source it's coming from is not. This is the origin of the confusion for cherry-pick.

You can resolve this situation with a git cherry-pick --skip, but why should you have to?

I've adjusted the script to use git merge, which absolutely does figure it out when the changes are identical and properly no-ops without getting into an error state.

@azure-sdk
Copy link
Collaborator

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants