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

refusing to merge unrelated histories #37

Closed
BigMichi1 opened this issue Oct 26, 2021 · 4 comments
Closed

refusing to merge unrelated histories #37

BigMichi1 opened this issue Oct 26, 2021 · 4 comments

Comments

@BigMichi1
Copy link

suddenly the action stoped working syncing with upstream. at that time I was using version 2.3 of the action,
see here:
https://github.com/BigMichi1/certbot-dns-hetzner/actions/runs/1367119281
https://github.com/BigMichi1/certbot-dns-hetzner/actions/runs/1367244674
between these two executions are 30 minutes and no change has been committed to both repositories at that time

now I tried also upgrading to version 3.1 of the action and now the error is different but still not being able to perform the sync
https://github.com/BigMichi1/certbot-dns-hetzner/runs/4008005789?check_suite_focus=true

the GitHub UI itself does not show anything to merge, also running the commands on command line do not result in one of the above errors

git clone git@github.com:BigMichi1/certbot-dns-hetzner.git
cd certbot-dns-hetzner/
git remote add upstream git@github.com:ctrlaltcoop/certbot-dns-hetzner.git
git fetch upstream master
git merge upstream/master

shows already up to date

@aormsby
Copy link
Owner

aormsby commented Oct 31, 2021

Well, I'm going to have to browse through your work a bit to get a better idea of what you're facing. Not sure I have time right away, though. In the meantime, maybe try v2.4. I made some significant changes in the move to v3, and it's possible that it's not immediately compatible with your setup. However, v2.4 runs with the same flow as v2.3 with some fixes. Worth a shot.

@aormsby
Copy link
Owner

aormsby commented Oct 31, 2021

Also try this -- https://github.com/aormsby/Fork-Sync-With-Upstream-action/wiki/Scenarios-for-Advanced-Input#when-your-target-and-upstream-branches-dont-share-a-common-ancestor

upstream_pull_args: '--allow-unrelated-histories'

That could be your solution. However, please note there is another bug you might run into detailed here -- #36. I'm working on that next.

@Wyn-Price
Copy link

Wyn-Price commented Nov 11, 2021

Using #38 fixed this for me (uses: aormsby/Fork-Sync-With-Upstream-action@check-fix-2 )

@aormsby
Copy link
Owner

aormsby commented Nov 26, 2021

#38 merged, released as v3.2

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

No branches or pull requests

3 participants