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

Fix "refusing to merge unrelated histories" #3626

Merged
merged 1 commit into from
May 6, 2024

Conversation

ysaito1001
Copy link
Contributor

Motivation and Context

Fixes the last failed backport workflow run

Description

The error refusing to merge unrelated histories was caused by the same reason described in prior PRs (#3479, #3480). We need to tell git unshallow histories so that it knows they are actually related.

Testing

Ran the failed workflow from this branch and successfully generated a backport PR3625.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ysaito1001 ysaito1001 requested review from a team as code owners May 6, 2024 16:42
@ysaito1001 ysaito1001 enabled auto-merge May 6, 2024 16:57
Copy link

github-actions bot commented May 6, 2024

A new generated diff is ready to view.

  • No codegen difference in the AWS SDK
  • No codegen difference in the Client Test
  • No codegen difference in the Server Test
  • No codegen difference in the Server Test Python
  • No codegen difference in the Server Test Typescript

A new doc preview is ready to view.

@ysaito1001 ysaito1001 added this pull request to the merge queue May 6, 2024
Merged via the queue into main with commit 9d2b0dd May 6, 2024
45 checks passed
@ysaito1001 ysaito1001 deleted the ysaito/fetch-unshallow-to-fix-unrelated-histories branch May 6, 2024 17:38
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.

3 participants