From 3069b4a78dfd6316e50e55c38f42861cde18c6fc Mon Sep 17 00:00:00 2001
From: shahabhijeet <abhishah@microsoft.com>
Date: Fri, 15 Feb 2019 17:34:01 -0800
Subject: [PATCH] moving pr template to it's own directory to start using the
 new feature work-in-progress introduced for github PRs

---
 .../PULL_REQUEST_TEMPLATE.md                  | 54 +++++++++----------
 1 file changed, 27 insertions(+), 27 deletions(-)
 rename .github/{ => PULL_REQUEST_TEMPLATE}/PULL_REQUEST_TEMPLATE.md (98%)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
similarity index 98%
rename from .github/PULL_REQUEST_TEMPLATE.md
rename to .github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
index 571f64265200..54760fee4786 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
@@ -1,27 +1,27 @@
-<!-- DO NOT DELETE THIS TEMPLATE -->
-
-## Description
-<!--
-Please add an informative description that covers that changes made by the pull request.
-
-If you are regenerating your SDK based off of a new swagger spec, please add the link to the corresponding swagger spec pull request that has been merged in the azure-rest-api-specs repository
--->
-
----
-
-This checklist is used to make sure that common guidelines for a pull request are followed.
-- [ ] Please add REST spec PR link to the SDK PR
-- [ ] **I have read the [contribution guidelines](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/.github/CONTRIBUTING.md).**
-- [ ] **The pull request does not introduce [breaking changes](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/Documentation/breaking-changes.md).**
-
-### [General Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/.github/CONTRIBUTING.md#general-guidelines)
-- [ ] Title of the pull request is clear and informative.
-- [ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, [see this page](https://github.com/Azure/azure-powershell/blob/dev/documentation/cleaning-up-commits.md).
-
-### [Testing Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/.github/CONTRIBUTING.md#testing-guidelines)
-- [ ] Pull request includes test coverage for the included changes.
-
-### [SDK Generation Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/.github/CONTRIBUTING.md#sdk-generation-guidelines)
-- [ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
-- [ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
-- [ ] The `*.csproj` and `AssemblyInfo.cs` files have been updated with the new version of the SDK.
+<!-- DO NOT DELETE THIS TEMPLATE -->
+
+## Description
+<!--
+Please add an informative description that covers that changes made by the pull request.
+
+If you are regenerating your SDK based off of a new swagger spec, please add the link to the corresponding swagger spec pull request that has been merged in the azure-rest-api-specs repository
+-->
+
+---
+
+This checklist is used to make sure that common guidelines for a pull request are followed.
+- [ ] Please add REST spec PR link to the SDK PR
+- [ ] **I have read the [contribution guidelines](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/.github/CONTRIBUTING.md).**
+- [ ] **The pull request does not introduce [breaking changes](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/Documentation/breaking-changes.md).**
+
+### [General Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/.github/CONTRIBUTING.md#general-guidelines)
+- [ ] Title of the pull request is clear and informative.
+- [ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, [see this page](https://github.com/Azure/azure-powershell/blob/dev/documentation/cleaning-up-commits.md).
+
+### [Testing Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/.github/CONTRIBUTING.md#testing-guidelines)
+- [ ] Pull request includes test coverage for the included changes.
+
+### [SDK Generation Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/.github/CONTRIBUTING.md#sdk-generation-guidelines)
+- [ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
+- [ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
+- [ ] The `*.csproj` and `AssemblyInfo.cs` files have been updated with the new version of the SDK.