From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] CI on own fork always fails because the branch is out of date albeit it isn't
Date: Wed, 11 Jan 2023 00:07:38 +0100 [thread overview]
Message-ID: <20230110230738.1PfL4gokoiYD8YzaJszTMoQogZumntNwEepursoaCG4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41376@inbox.vuxu.org>
[-- 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
prev parent reply other threads:[~2023-01-10 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 10:53 [ISSUE] " steinex
2022-12-31 14:20 ` classabbyamp
2022-12-31 14:43 ` steinex
2022-12-31 14:43 ` steinex
2022-12-31 14:44 ` steinex
2022-12-31 14:49 ` classabbyamp
2023-01-04 22:10 ` Chocimier
2023-01-07 12:51 ` classabbyamp
2023-01-08 18:59 ` steinex
2023-01-10 23:07 ` classabbyamp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230110230738.1PfL4gokoiYD8YzaJszTMoQogZumntNwEepursoaCG4@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).