GitLab CI: Add aarch64-linux-deb{10,11}

[chreekat]

GitLab pipeline:

Makes headway on #8849

Kudos to @hasufell for making this possible with a fix to GHCUp

[Mikolaj]

ghc-prerelease jobs failing is normal right now. We are working on this.

[Mikolaj]

LGTM

[Mikolaj]

@mergify backport 3.10

[mergify]

backport 3.10

✅ Backports have been created

• #8867 GitLab CI: Add aarch64-linux-deb{10,11} (backport #8851) has been created for branch 3.10

[Mikolaj]

Let me set the label, not to distract the author.

[chreekat]

@Mikolaj I assumed it was a maintainer responsibility to do whatever action is required to merge a PR. :) If it's up to the author, are the steps documented somewhere?

[Mikolaj]

Yes, in https://github.com/haskell/cabal/blob/master/CONTRIBUTING.md#github-pull-request-conventions

Is that readable enough?

[ulysses4ever]

@chreekat @Mikolaj The merge process is stuck for some reason. I suggest to rebase on master. Can be done from the web with a comment @Mergify rebase on this thread.

[chreekat]

I'll give it a shot:

@mergify rebase

[chreekat]

@Mikolaj thanks for the link! I like the policy. It's just a bit hard to find as a first-time contributor. I don't feel too bad that I didn't read such a long CONTRIBUTING.md from top to bottom :D

[ulysses4ever]

@chreekat you have to create a comment with exactly that text and nothing else (the bot is silly)

Also, just fyi, PR template references exactly the section about PR guidelines in CONTRIBUTING.md

[Mikolaj]

@mergify refresh

[mergify]

refresh

✅ Pull request refreshed

[chreekat]

PR template references exactly the section about PR guidelines in CONTRIBUTING.md

Does it, though? :)

[Mikolaj]

Strange, the Queue: Embarked in merge train link says

The merge queue pull request can't be updated
Details:

    Unable to update: user chreekat is unknown.

    Please make sure chreekat has logged in Mergify dashboard.

[ulysses4ever]

@chreekat you're right: out references some sections but not that one. We should update it!

@Mikolaj indeed, this is the error I saw yesterday. I have no clue what's wrong. But then again, I didn't try to Google it even...

[Mikolaj]

Let's hope @chreekat can at least rebase via mergify invocation.

[chreekat]

@mergify rebase

[mergify]

rebase

❌ Unable to rebase: user chreekat is unknown.

Please make sure chreekat has logged in Mergify dashboard.

[chreekat]

🙈

[ulysses4ever]

Crap, it looks like Mergify without Premium quickly becomes more and more useless:

• Can't embark on merge train: Unable to update: user X is unknown. Mergifyio/mergify#5075
• https://changelog.mergify.com/changelog/rebasing-pull-requests-with-a-random-user-is-deprecated

My understanding after quick skimming: only admins will be able to rebase their own PRs via Mergify unless you have Premium and can set update_bot_account.

[Mikolaj]

That would be a very ugly bait and switch. But they say they are going to fix it, so probably unintentional.

[Mikolaj]

@mergify rebase

[mergify]

rebase

✅ Branch has been successfully rebased