From dd1d25c5aa22a2eb1bac6a15c25a2e83080d234c Mon Sep 17 00:00:00 2001 From: Sami Jaber Date: Wed, 21 Dec 2022 11:18:51 -0400 Subject: [PATCH] Update bug_report.yaml (#962) * Update bug_report.yaml * Update bug_report.yaml --- .github/ISSUE_TEMPLATE/bug_report.yaml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yaml index e7d4b26a74..268b003440 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yaml +++ b/.github/ISSUE_TEMPLATE/bug_report.yaml @@ -1,13 +1,15 @@ name: 🐞 Bug Report -description: Something does not work or is flaky: let us know! +description: Something does not work or is flaky? let us know! labels: [bug, triage] body: - type: markdown attributes: value: | - Thanks for taking the time to fill out this bug report. Please bear in mind that we are a _very_ small and lean team, and the surface area of Mitosis is fairly large due to the nature of the project. - As the tool is in beta and under active development, we ask for your patience and help in contributing to this amazing project. - We always do our best to empower folks to contribute substantially to the project and quickly have an impact. + Thanks for taking the time to fill out this bug report! We are actively looking for folks interested in becoming active contributors to Mitosis. Given its large surface area, there is a ton of room for any engineer to make a large and sustained impact on the project. + + We invest a ton of time in helping newcomers get onboarded to the project and teach them how to make changes to the codebase ([example1](https://github.com/BuilderIO/mitosis/issues/847#issuecomment-1307439504), [example2](https://github.com/BuilderIO/mitosis/issues/372#issuecomment-1133471614), [example3](https://github.com/BuilderIO/mitosis/issues/734#issuecomment-1255453702)). + + So consider ticking that "Yes" box below, and we'll do our best to set you up for success. 🙂 - type: dropdown id: help-fix validations: