lix-project/hydra
4
0
Fork 6
Code Issues 2 Pull requests Packages Projects Releases Wiki Activity

README: document release branches #16

Merged
ma27 merged 1 commit from ma27/hydra:readme-branches into main 2024-12-06 16:34:59 +00:00
Conversation 3 Commits 1 Files changed 1 +11
ma27 commented 2024-12-04 09:27:59 +00:00
Member
Copy link

Closes #12
cc @benaryorg

@vriska do you have the necessary permissions to set up branch protection for lix-2.91? I think I'm a collaborator only, so I don't see the settings tab here.
I'd be more comfortable if we could do that before merging this.

Closes #12 cc @benaryorg @vriska do you have the necessary permissions to set up branch protection for `lix-2.91`? I think I'm a collaborator only, so I don't see the settings tab here. I'd be more comfortable if we could do that before merging this.
ma27 added 1 commit 2024-12-04 09:28:05 +00:00 
Closes #12
benaryorg commented 2024-12-05 02:01:26 +00:00
First-time contributor
Copy link

LGTM

Given that I was already on 799441dcf6 and moving to f19d82e291 only includes a flake pin (which is irrelevant to me since I override all the flake inputs using those from my mirror anyway) there isn't much that can break on my end (just to be safe I built checks.x86_64-linux.{install,build} which do succeed).
However being able to commit the branch changes to a downsteam flake and getting them to build with the new lix-2.91 branch means that the branches work, and that the documentation herein is correct.

So much for the user side, thank you very much!

LGTM Given that I was already on 799441dcf6d595efb0def686ca0815aef398627b and moving to f19d82e2916c154d9750e962b7d790344211739b only includes a flake pin (which is irrelevant to me since I override all the flake inputs using those from my mirror anyway) there isn't much that can break on my end (just to be safe I built `checks.x86_64-linux.{install,build}` which do succeed). However being able to [commit the branch changes to a downsteam flake](https://git.shell.bsocat.net/infra/commit/?h=64875515728c6245613bb12bee94c1ab71af5e8f) and [getting them to build with the new *lix-2.91* branch](https://hydra.shell.bsocat.net/build/24392) means that the branches work, and that the documentation herein is correct. So much for the user side, thank you very much!
ma27 merged commit 42c4a85ec8 into main 2024-12-06 16:34:59 +00:00
ma27 deleted branch readme-branches 2024-12-06 16:35:11 +00:00
vriska commented 2024-12-09 21:35:52 +00:00
Member
Copy link

@vriska do you have the necessary permissions to set up branch protection for lix-2.91? I think I'm a collaborator only, so I don't see the settings tab here.

@ma27 I don't, sorry. Looking at the organization I'm not sure anyone not on the core team does?

> @vriska do you have the necessary permissions to set up branch protection for lix-2.91? I think I'm a collaborator only, so I don't see the settings tab here. @ma27 I don't, sorry. Looking at the organization I'm not sure anyone not on the core team does?
ma27 commented 2024-12-16 16:07:33 +00:00
Author
Member
Copy link

Sorry, should've mentioned it here as well: Jade took are of it after asking in Matrix.

Sorry, should've mentioned it here as well: Jade took are of it after asking in Matrix.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/hydra#16
No description provided.
Delete branch "ma27/hydra:readme-branches"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?