From 69a21076f5f6aaf1b9a14c55dedf5b6e91049e16 Mon Sep 17 00:00:00 2001 From: Lamparter Date: Sun, 21 Jul 2024 10:42:53 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=A7=91=E2=80=8D=F0=9F=92=BB=20Change=20'A?= =?UTF-8?q?PI=20changes'=20to=20'Required=20changes'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: 0x5bfa <62196528+0x5bfa@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/feature_request.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml index 2fd14d935..9e5875b34 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -23,8 +23,8 @@ body: - type: textarea id: api-changes attributes: - label: ⚡ API Changes - description: Include a list of all API changes, additions, subtractions as would be required by your proposal. These APIs should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some example (pseudo-)code of usage of your new API. + label: ⚡ Required changes + description: Include a list of all API changes in the code, i.e. additions, subtractions as would be required by your proposal. These APIs should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some example (pseudo-)code of usage of your new API. placeholder: | ```csharp var button = new Button ();