ahuston-0/nix-dotfiles
1
0
Fork 0
Code Issues Pull Requests 2 Actions 1 Packages Projects Releases Wiki Activity

update flake lock, resolve warnings and helvum decom #187

Merged
ahuston-0 merged 1 commits from update_flake_lock_action into main 2026-03-11 00:28:51 -04:00
Conversation 0 Commits 1 Files Changed 4 +34 -36
ahuston-0 commented 2026-03-11 00:22:19 -04:00
Owner
Copy Link
No description provided.
ahuston-0 force-pushed update_flake_lock_action from 4ade1b5996 to 0f8b574207 2026-03-11 00:25:10 -04:00 Compare
ahuston-0 scheduled this pull request to auto merge when all checks succeed 2026-03-11 00:25:17 -04:00
ahuston-0 merged commit e91c22ed44 into main 2026-03-11 00:28:51 -04:00
ahuston-0 deleted branch update_flake_lock_action 2026-03-11 00:28:52 -04:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
automated
PR was automatically generated (through a bot or CI/CD)
 bug
Something is not working
 dependencies
Used for PR's related to flake.lock updates
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ahuston-0
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ahuston-0/nix-dotfiles#187
Delete Branch "update_flake_lock_action"

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?