From f406ecf3eabe968a1b2d41faf304e05eb5d2a9ed Mon Sep 17 00:00:00 2001 From: Kuba Martin Date: Mon, 4 Sep 2023 16:38:47 +0200 Subject: [PATCH] Improve RFC description formatting. (#261) Signed-off-by: Jakub Martin --- .github/ISSUE_TEMPLATE/rfc.yml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/rfc.yml b/.github/ISSUE_TEMPLATE/rfc.yml index 3564db885c..bc70b28062 100644 --- a/.github/ISSUE_TEMPLATE/rfc.yml +++ b/.github/ISSUE_TEMPLATE/rfc.yml @@ -7,12 +7,13 @@ body: - type: markdown attributes: value: | - Thank you for opening an RFC! RFCs are a highly-structured format for submitting change requests. - All major changes to OpenTF should first go through an RFC, to have a place for the community to discuss. - The template has a lot of fields and is inspired by the Rust RFC template. - Please take your time to fill it out carefully. - Working experimental PoCs in a draft Pull Request are a very welcome attachment to an RFC, especially - ones that are easy to check out and take for a spin. + Thank you for opening an RFC! + + RFCs are a highly-structured format for submitting change requests. All major changes to OpenTF should first go through an RFC, to have a place for the community to discuss. + + The template has a lot of fields and is inspired by the Rust RFC template. Please take your time to fill it out carefully. + + Working experimental PoCs in a draft Pull Request are a very welcome attachment to an RFC, especially ones that are easy to check out and take for a spin. - type: textarea id: summary