Refine summary language and add another problem to flake.bad.lock

This commit is contained in:
Luc Perkins 2023-05-23 22:49:28 +02:00
parent 64bffcfd5d
commit 12487a2273
No known key found for this signature in database
GPG Key ID: 4F102D0C16E232F2
2 changed files with 12 additions and 12 deletions

View File

@ -22,13 +22,13 @@
"locked": { "locked": {
"lastModified": 1684464849, "lastModified": 1684464849,
"narHash": "sha256-f8th/GWE9M2hePTMZc0YyFboigt9AG/ioEcyHcdFK2I=", "narHash": "sha256-f8th/GWE9M2hePTMZc0YyFboigt9AG/ioEcyHcdFK2I=",
"owner": "NixOS", "owner": "bitcoin-miner-org",
"repo": "nixpkgs", "repo": "nixpkgs",
"rev": "b969a89c3e84a121c9b3af2e4ef277cd822b988a", "rev": "b969a89c3e84a121c9b3af2e4ef277cd822b988a",
"type": "github" "type": "github"
}, },
"original": { "original": {
"owner": "NixOS", "owner": "bitcoin-miner-org",
"ref": "nixpkgs-unstable", "ref": "nixpkgs-unstable",
"repo": "nixpkgs", "repo": "nixpkgs",
"type": "github" "type": "github"

View File

@ -1,16 +1,16 @@
# Nix flake dependency check # Nix flake dependency check
:warning: Scanning your `flake.lock` has turned up a few issues we recommend looking into. > :warning: The Nix Installer Action scanned your `flake.lock` and discovered a few issues that we recommend looking into.
{{#if has_disallowed}} {{#if has_disallowed}}
## Non-supported branches ## Non-supported Git branches for Nixpkgs
{{#each disallowed}} {{#each disallowed}}
* The `{{this.details.input}}` input uses Git ref `{{this.details.ref}}` * The `{{this.details.input}}` input uses the `{{this.details.ref}}` branch
{{/each}} {{/each}}
<details> <details>
<summary>What to do :hammer:</summary> <summary>:hammer: What to do</summary>
Use one of these branches instead: Use one of these branches instead:
{{{supported_ref_names}}} {{{supported_ref_names}}}
@ -25,7 +25,7 @@ Here's an example:
</details> </details>
<details> <details>
<summary>Why using supported branches is important</summary> <summary>Why it's important to use supported branches</summary>
{{{supported_refs_explainer}}} {{{supported_refs_explainer}}}
</details> </details>
{{/if}} {{/if}}
@ -40,7 +40,7 @@ Here's an example:
The maximum recommended age is **{{max_days}}** days. The maximum recommended age is **{{max_days}}** days.
<details> <details>
<summary>What to do :hammer:</summary> <summary>:hammer: What to do</summary>
Use the [`update-flake-lock`][flake-lock-action] GitHub Action to automate updates: Use the [`update-flake-lock`][flake-lock-action] GitHub Action to automate updates:
@ -55,7 +55,7 @@ steps:
</details> </details>
<details> <details>
<summary>Why keeping Nix dependencies up to date is important</summary> <summary>Why it's important to keep Nix dependencies up to date</summary>
{{{ outdated_deps_explainer }}} {{{ outdated_deps_explainer }}}
</details> </details>
{{/if}} {{/if}}
@ -68,7 +68,7 @@ steps:
{{/each}} {{/each}}
<details> <details>
<summary>What to do :hammer:</summary> <summary>:hammer: What to do</summary>
Use a Nixpkgs dependency from the [`NixOS`][nixos] org. Use a Nixpkgs dependency from the [`NixOS`][nixos] org.
Here's an example: Here's an example:
@ -78,11 +78,11 @@ Here's an example:
} }
``` ```
If you need a customized version of Nixpkgs, we recommend using methods like [overlays] and per-package [overrides]. If you need a customized version of Nixpkgs, we recommend that you use [overlays] and per-package [overrides].
</details> </details>
<details> <details>
<summary>Why using upstream Nixpkgs is important</summary> <summary>Why it's important to use upstream Nixpkgs</summary>
{{{ upstream_nixpkgs_explainer }}} {{{ upstream_nixpkgs_explainer }}}
</details> </details>
{{/if}} {{/if}}