summaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorFernando Rodrigues <alpha@sigmasquadron.net>2025-04-17 21:55:23 +0000
committerFernando Rodrigues <alpha@sigmasquadron.net>2025-04-17 21:59:54 +0000
commit8405b2bf621971b7c9d5f9610c710d5f774462ba (patch)
treeffb30e6c93ac56029de79aed8e11af601f514003 /.github
parentnixos/anubis: init module (#392018) (diff)
downloadnixpkgs-8405b2bf621971b7c9d5f9610c710d5f774462ba.tar.gz
ISSUE_TEMPLATES: Remove note about forks from the Update Request form
The Package Request form no longer exists, so it makes no sense to mention it. We used to direct update requests to forks there, instead, users can now mention forks in the Additional Context section added in this commit. Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
Diffstat (limited to '.github')
-rw-r--r--.github/ISSUE_TEMPLATE/05_update_request.yml10
1 files changed, 7 insertions, 3 deletions
diff --git a/.github/ISSUE_TEMPLATE/05_update_request.yml b/.github/ISSUE_TEMPLATE/05_update_request.yml
index 4b29a2af0126..91944dbd9cf5 100644
--- a/.github/ISSUE_TEMPLATE/05_update_request.yml
+++ b/.github/ISSUE_TEMPLATE/05_update_request.yml
@@ -22,9 +22,6 @@ body:
> For instance, if you were filing a request against the out of date `hello` package, where the current version in Nixpkgs is 1.0.0, but the latest version upstream is 1.0.1, your title would be as follows:
> `Update Request: hello 1.0.0 → 1.0.1`
- > [!NOTE]
- > If you are filing an update request to change a package's source to a fork, please file a new package request instead. Even if the original upstream is outdated, the fork should be considered a new package.
-
---
- type: "dropdown"
id: "version"
@@ -75,6 +72,13 @@ body:
validations:
required: false
- type: "textarea"
+ id: "additional-context"
+ attributes:
+ label: "Additional context"
+ description: "Add any other context about the update here."
+ validations:
+ required: false
+ - type: "textarea"
id: "maintainers"
attributes:
label: "Notify maintainers"