[ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't

[ISSUE] CI on own fork always fails because the branch is out of date albeit it isn't

[steinex]

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

New issue by steinex on void-packages repository

https://github.com/void-linux/void-packages/issues/41376

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.1_1 x86_64 AuthenticAMD notuptodate hold rrrmDFFFFFFFFFFF

### Package(s) Affected

no specific package

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/steinex/void-packages/pull/230
https://github.com/steinex/void-packages/pull/227

### Expected behaviour

CI should run as usual.

### Actual behaviour

To check if my package builds for all archs, I always open a PR on my own branch first for QA. This stopped working with the problem:
```
Error: Your branch is too out of date. Please rebase on upstream and force-push.
Error: Process completed with exit code 1.
```

This does only happen on my own branch, if I push directly to void-packages everything is fine.


### Steps to reproduce

1. Prepare a PR
2. Push to own branch
3. See CI failing

Re: CI on own fork always fails because the branch is out of date albeit it isn't

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 392 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368221717

Comment:
is the master branch on your fork up-to-date with the master branch of the main repo?

you could also try running parts of this script manually locally: https://github.com/void-linux/void-packages/blob/master/common/travis/changed_templates.sh

Re: CI on own fork always fails because the branch is out of date albeit it isn't

[steinex]

[-- Attachment #1: Type: text/plain, Size: 344 bytes --]

New comment by steinex on void-packages repository

https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368224563

Comment:
Yes, the master branch of my fork is up-to date. The script you mentions gives nothing besides

```
Changed packages:
```

So I assume that means there are no changed between my fork and master.

Re: CI on own fork always fails because the branch is out of date albeit it isn't

[steinex]

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

New comment by steinex on void-packages repository

https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368224563

Comment:
Yes, the master branch of my fork is up-to date. The script you mention gives nothing besides

```
Changed packages:
```

So I assume that means there are no changed between my fork and master.

Re: CI on own fork always fails because the branch is out of date albeit it isn't

[steinex]

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

New comment by steinex on void-packages repository

https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368224563

Comment:
Yes, the master branch of my fork is up-to date. The script you mention gives nothing besides

```
Changed packages:
```

So I assume that means there are no changes between my fork and master.

Re: CI on own fork always fails because the branch is out of date albeit it isn't

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 330 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368225218

Comment:
hm not in a spot to debug this atm but it appears to be cloning your fork as the master branch and the pr branch so that shouldn't be an issue. maybe someone else can find the issue

Re: CI on own fork always fails because the branch is out of date albeit it isn't

[Chocimier]

[-- Attachment #1: Type: text/plain, Size: 249 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/41376#issuecomment-1371488873

Comment:
changed_templates.sh uses FETCH_HEAD, which after full clone is set to random branch rather than master

Re: CI on own fork always fails because the branch is out of date albeit it isn't

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 220 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/41376#issuecomment-1374471176

Comment:
maybe switching that line to `git merge-base master "$tip"` would work?

Re: CI on own fork always fails because the branch is out of date albeit it isn't

[steinex]

[-- Attachment #1: Type: text/plain, Size: 280 bytes --]

New comment by steinex on void-packages repository

https://github.com/void-linux/void-packages/issues/41376#issuecomment-1374903776

Comment:
> maybe switching that line to `git merge-base master "$tip"` would work?

I gave this a try. Unfortunately it didn't change anything.

Re: [ISSUE] [CLOSED] CI on own fork always fails because the branch is out of date albeit it isn't

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Closed issue by steinex on void-packages repository

https://github.com/void-linux/void-packages/issues/41376

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.1_1 x86_64 AuthenticAMD notuptodate hold rrrmDFFFFFFFFFFF

### Package(s) Affected

no specific package

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/steinex/void-packages/pull/230
https://github.com/steinex/void-packages/pull/227

### Expected behaviour

CI should run as usual.

### Actual behaviour

To check if my package builds for all archs, I always open a PR on my own branch first for QA. This stopped working with the problem:
```
Error: Your branch is too out of date. Please rebase on upstream and force-push.
Error: Process completed with exit code 1.
```

This does only happen on my own branch, if I push directly to void-packages everything is fine.


### Steps to reproduce

1. Prepare a PR
2. Push to own branch
3. See CI failing