If you're retargetting a pull request and want to avoid notifying the code owners for all the unrelated changes, first rebase it against the merge base of master and staging, e.g. `git rebase --onto $(git merge-base origin/master origin/staging) master` if changing from master to staging.
Though not sure about the last `master` there. I usually do `HEAD~<number of commits you want to rebase>` instead
Then force push, then change the branch in the github ui
the aarch64 and darwin builders have a lot of trouble keeping up again
cole-h has quit [Ping timeout: 260 seconds]
lopsided98_ has joined #nixos-dev
lopsided98 has quit [Ping timeout: 260 seconds]
Is anyone actively working on/using incremental builds with Nix?
qyliss has quit [Quit: bye]
qyliss has joined #nixos-dev
FRidh: darwin is pretty good at catching up
most of macs were re-added ~2 days ago
aach64 goes in batches depending on market value
infinisil: good point. I think my mistake was to push the merge-base first without the additional commit
infinisil's karma got increased to 374
Oh yeah that would kind of explain it :)
Mic92 has quit [Quit: WeeChat 2.9]
Mic92 has joined #nixos-dev
__red__ has joined #nixos-dev
Is this the right place to ask for help with hydra?