Skip to content

ci: Dogfood Nix from master (backport #13473)#13536

Merged
mergify[bot] merged 3 commits into2.28-maintenancefrom
mergify/bp/2.28-maintenance/pr-13473
Jul 24, 2025
Merged

ci: Dogfood Nix from master (backport #13473)#13536
mergify[bot] merged 3 commits into2.28-maintenancefrom
mergify/bp/2.28-maintenance/pr-13473

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jul 24, 2025

Motivation

This would allow us to catch bugs (especially MacOS ones) much earlier before release.

Context

Resolves #12462


Add 👍 to pull requests you find important.

The Nix maintainer team uses a GitHub project board to schedule and track reviews.


This is an automatic backport of pull request #13473 done by [Mergify](https://mergify.com).

@mergify mergify bot requested a review from edolstra as a code owner July 24, 2025 17:09
@mergify mergify bot added automatic backport This PR is a backport produced by automation (does not trigger backporting) conflicts merge-queue labels Jul 24, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Jul 24, 2025

Cherry-pick of 04f6974 has failed:

On branch mergify/bp/2.28-maintenance/pr-13473
Your branch is up to date with 'origin/2.28-maintenance'.

You are currently cherry-picking commit 04f6974d2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   .github/actions/install-nix-action/action.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/ci.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@mergify mergify bot added conflicts automatic backport This PR is a backport produced by automation (does not trigger backporting) labels Jul 24, 2025
xokdvium and others added 3 commits July 24, 2025 23:13
(cherry picked from commit 04f6974)
This should provide more coverage for the build from master that
is being dogfooded.

(cherry picked from commit 3b3c021)
CI on release branches should be stable, otherwise backporting
might become flaky and unreliable. Dogfooding only really makes
sense for CI on master branch, where failures are not as tedious
to work around.
@xokdvium xokdvium force-pushed the mergify/bp/2.28-maintenance/pr-13473 branch from c866266 to c56833e Compare July 24, 2025 20:16
mergify bot added a commit that referenced this pull request Jul 24, 2025
@mergify mergify bot merged commit ec4707d into 2.28-maintenance Jul 24, 2025
27 checks passed
@mergify mergify bot deleted the mergify/bp/2.28-maintenance/pr-13473 branch July 24, 2025 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automatic backport This PR is a backport produced by automation (does not trigger backporting) merge-queue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant