flake.lock: update #74

Merged

modulatingforce merged 1 commit from flake-lock-update into master

2024-04-09 08:47:36 -04:00

WoodpeckerCI commented

2024-04-08 21:04:35 -04:00

Collaborator

PR automatically created by Woodpecker CI

WoodpeckerCI added 1 commit 2024-04-08 21:04:35 -04:00

flake.lock: update dd2670c766

modulatingforce self-assigned this 2024-04-09 07:38:07 -04:00

modulatingforce commented

2024-04-09 07:57:34 -04:00

Owner

@notohh is this what u mentioned yesterday?

I know this is muniWAYTOODANK for me; I'm thinking this type of PR will happen periodically and curious how this should be labeled for PRs like this (maintenance? or CI/CD?) I also believe we've had these in our previous bot, but :giggles: I wanna make use of labelling here

Also, I know nothing about Nix LULE (and I need to read more https://nixos.org/ ) , and I know I've asked these before :

Is there a very brief high level description of what this change entails ?
Understanding that each branch ofc will have to merge / rebase these changes from master , is there anything required for other branches or anything done locally?

This sounds more applicable to forge or deployment level, wherever you're choosing to deploy, and we won't have to change the way we're making changes locally

Just checking! Thanks!

@notohh is this what u mentioned yesterday? I know this is muniWAYTOODANK for me; I'm thinking this type of PR will happen periodically and curious how this should be labeled for PRs like this (`maintenance`? or `CI/CD`?) I also believe we've had these in our previous bot, but :giggles: I wanna make use of labelling here Also, I know nothing about Nix LULE (and I need to read more https://nixos.org/ ) , and I know I've asked these before : 1. Is there a very brief high level description of what this change entails ? 2. Understanding that each branch ofc will have to merge / rebase these changes from `master` , is there anything required for other branches or anything done locally? This sounds more applicable to forge or deployment level, wherever you're choosing to deploy, and we won't have to change the way we're making changes locally Just checking! Thanks!

modulatingforce changed title from ~~flake.lock: update~~ to WIP: flake.lock: update

2024-04-09 07:57:44 -04:00

modulatingforce commented

2024-04-09 08:02:33 -04:00

Owner

or :danki: I'm also fine with auto approving without labeling - I see that was done before - that might make sense

notohh commented

2024-04-09 08:43:19 -04:00

Owner

Is there a very brief high level description of what this change entails ?

nothing high level about it really, just package updates

Understanding that each branch ofc will have to merge / rebase these changes from master , is there anything required for other branches or anything done locally?

there probably shouldnt be. might have to rebase your working branches once a month whenever this automated pr runs

This sounds more applicable to forge or deployment level, wherever you're choosing to deploy, and we won't have to change the way we're making changes locally

pretty much yeah. this keeps my local packages up to date, same will go for ci.

> 1. Is there a very brief high level description of what this change entails ? nothing high level about it really, just package updates > 2. Understanding that each branch ofc will have to merge / rebase these changes from `master` , is there anything required for other branches or anything done locally? there probably shouldnt be. might have to rebase your working branches once a month whenever this automated pr runs > This sounds more applicable to forge or deployment level, wherever you're choosing to deploy, and we won't have to change the way we're making changes locally pretty much yeah. this keeps my local packages up to date, same will go for ci.