Remove unnecessary line breaks in issue templates (mlflow#2810)

.github/ISSUE_TEMPLATE/bug_report_template.md

@@ -4,14 +4,12 @@ about: Use this template for reporting bugs encountered while using MLflow.
 labels: 'bug'
 title: "[BUG]"
 ---
-Thank you for submitting an issue. Please refer to our [issue policy](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md)
-for additional information about bug reports. For help with debugging your code, please refer to [Stack Overflow](https://stackoverflow.com/questions/tagged/mlflow).
+Thank you for submitting an issue. Please refer to our [issue policy](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md) for additional information about bug reports. For help with debugging your code, please refer to [Stack Overflow](https://stackoverflow.com/questions/tagged/mlflow).
 
 **Please fill in this bug report template to ensure a timely and thorough response.**
 
 ### Willingness to contribute
-The MLflow Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix
-for this bug to the MLflow code base?
+The MLflow Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the MLflow code base?
 
 - [ ] Yes. I can contribute a fix for this bug independently.
 - [ ] Yes. I would be willing to contribute a fix for this bug with guidance from the MLflow community.
@@ -33,8 +31,7 @@ Describe the problem clearly here. Include descriptions of the expected behavior
 Provide a reproducible test case that is the bare minimum necessary to generate the problem.
 
 ### Other info / logs
-Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks,
-please include the full traceback. Large logs and files should be attached.
+Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
 
 
 ### What component(s), interfaces, languages, and integrations does this bug affect?

.github/ISSUE_TEMPLATE/doc_fix_template.md

@@ -4,14 +4,12 @@ about: Use this template for proposing documentation fixes/improvements.
 labels: 'area/docs'
 title: "[DOC-FIX]"
 ---
-Thank you for submitting an issue. Please refer to our [issue policy](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md)
-for information on what types of issues we address.
+Thank you for submitting an issue. Please refer to our [issue policy](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md) for information on what types of issues we address.
 
 **Please fill in this documentation issue template to ensure a timely and thorough response.**
 
 ### Willingness to contribute
-The MLflow Community encourages documentation fix contributions. Would you or another member of your organization be willing to
-contribute a fix for this documentation issue to the MLflow code base?
+The MLflow Community encourages documentation fix contributions. Would you or another member of your organization be willing to contribute a fix for this documentation issue to the MLflow code base?
 
 - [ ] Yes. I can contribute a documentation fix independently.
 - [ ] Yes. I would be willing to contribute a document fix with guidance from the MLflow community.
@@ -22,5 +20,4 @@ contribute a fix for this documentation issue to the MLflow code base?
 Please provide a link to the documentation entry in question.
 
 ### Description of proposal (what needs changing):
-Provide a clear description. Why is the proposed documentation
-better?
+Provide a clear description. Why is the proposed documentation better?

.github/ISSUE_TEMPLATE/feature_request_template.md

@@ -4,9 +4,7 @@ about: Use this template for feature and enhancement proposals.
 labels: 'enhancement'
 title: "[FR]"
 ---
-Thank you for submitting a feature request. **Before proceeding, please review MLflow's
-[Issue Policy for feature requests](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md#feature-requests)
-and the [MLflow Contributing Guide](https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.rst)**.
+Thank you for submitting a feature request. **Before proceeding, please review MLflow's [Issue Policy for feature requests](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md#feature-requests) and the [MLflow Contributing Guide](https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.rst)**.
 
 **Please fill in this feature request template to ensure a timely and thorough response.**
 
@@ -56,6 +54,4 @@ Integrations
 
 ## Details
 
-(Use this section to include any additional information about the feature. If you have a proposal
-for how to implement this feature, please include it here. For implementation guidelines, please
-refer to the [Contributing Guide](https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.rst#contribution-guidelines).)
+(Use this section to include any additional information about the feature. If you have a proposal for how to implement this feature, please include it here. For implementation guidelines, please refer to the [Contributing Guide](https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.rst#contribution-guidelines).)

.github/ISSUE_TEMPLATE/installation_issue_template.md

@@ -4,8 +4,7 @@ about: Use this template for reporting bugs encountered while installing MLflow.
 labels: 'bug'
 title: "[SETUP-BUG]"
 ---
-Thank you for submitting an issue. Please refer to our [issue policy](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md)
-for information on what types of issues we address.
+Thank you for submitting an issue. Please refer to our [issue policy](https://www.github.com/mlflow/mlflow/blob/master/ISSUE_POLICY.md) for information on what types of issues we address.
 
 **Please fill in this installation issue template to ensure a timely and thorough response.**
 
@@ -20,5 +19,4 @@ for information on what types of issues we address.
 Provide the exact sequence of commands / steps that you executed before running into the problem.
 
 ### Other info / logs
-Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks,
-please include the full traceback. Large logs and files should be attached.
+Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.