Toqozz / wired-notify

Lightweight notification daemon with highly customizable layout blocks, written in Rust.
MIT License
581 stars 27 forks source link

Update flake.lock #129

Closed github-actions[bot] closed 7 months ago

github-actions[bot] commented 8 months ago

Automated changes by the update-flake-lock GitHub Action.

Flake lock file updates:

• Updated input 'flake-parts':
    'github:hercules-ci/flake-parts/07f6395285469419cf9d078f59b5b49993198c00' (2024-01-11)
  → 'github:hercules-ci/flake-parts/b253292d9c0a5ead9bc98c4e9a26c6312e27d69f' (2024-02-01)
• Updated input 'flake-parts/nixpkgs-lib':
    'github:NixOS/nixpkgs/b0d36bd0a420ecee3bc916c91886caca87c894e9?dir=lib' (2023-12-30)
  → 'github:NixOS/nixpkgs/97b17f32362e475016f942bbdfda4a4a72a8a652?dir=lib' (2024-01-29)
• Updated input 'nixpkgs':
    'github:nixos/nixpkgs/eabe8d3eface69f5bb16c18f8662a702f50c20d5' (2024-01-09)
  → 'github:nixos/nixpkgs/6e2f00c83911461438301db0dba5281197fe4b3a' (2024-02-17)
• Updated input 'rust-overlay':
    'github:oxalica/rust-overlay/9e0af26ffe52bf955ad5575888f093e41fba0104' (2024-01-13)
  → 'github:oxalica/rust-overlay/c77e68d33a84ce3f9e86905c0f2ef78d5defad28' (2024-02-17)
• Updated input 'rust-overlay/flake-utils':
    'github:numtide/flake-utils/cfacdce06f30d2b68473a46042957675eebb3401' (2023-04-11)
  → 'github:numtide/flake-utils/1ef2e671c3b0c19053962c07dbda38332dcebf26' (2024-01-15)
• Updated input 'rust-overlay/nixpkgs':
    'github:NixOS/nixpkgs/96ba1c52e54e74c3197f4d43026b3f3d92e83ff9' (2023-04-13)
  → 'github:NixOS/nixpkgs/90f456026d284c22b3e3497be980b2e47d0b28ac' (2024-01-29)

Running GitHub Actions on this PR

GitHub Actions will not run workflows on pull requests which are opened by a GitHub Action.

To run GitHub Actions workflows on this PR, run:

git branch -D update_flake_lock_action
git fetch origin
git checkout update_flake_lock_action
git commit --amend --no-edit
git push origin update_flake_lock_action --force
Toqozz commented 7 months ago

So it seems like for some reason github won't let me add reviewers unless they are collaborators on the repository... which I did.

But then it seems like collaborators just have the same rights to the repository (or just "Issues"?) as everyone else, unless your repository is part of an organization, which is weird for obvious reasons.

Maybe I'll just have to manually tag you for those :(

TornaxO7 commented 7 months ago

Maybe I'll just have to manually tag you for those :(

No problem! :)