From 6fe36266a1890cc56fe376b26eebbccd0bc452b4 Mon Sep 17 00:00:00 2001 From: Rosario Pulella Date: Thu, 23 Sep 2021 14:23:59 -0400 Subject: [PATCH] Add more guidance on creating feature branches --- Create-and-Submit-PullRequest.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Create-and-Submit-PullRequest.md b/Create-and-Submit-PullRequest.md index 757d2a5..7fc365e 100644 --- a/Create-and-Submit-PullRequest.md +++ b/Create-and-Submit-PullRequest.md @@ -5,9 +5,9 @@ If this is your first time contributing to Windows Community Toolkit and never c Anyone can create a Pull Request by forking the Windows Community Toolkit repository. Here is how you can [Create a Pull Request from fork](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) -Once you fork the Windows Community Toolkit repo, it is essential to create all changes in a _feature branch_ of your forked repository. If you have the changes in the forked feature branch you can create a Pull Request in the main Windows Community Toolkit where your changes will be merged to the **main** branch. +Once you fork the Windows Community Toolkit repo, it is essential to create all changes in a _feature branch_ ( for example `add-listview-extensions` ) of your forked repository. If you have the changes in the forked feature branch you can create a Pull Request in the main Windows Community Toolkit where your changes will be merged to the **main** branch. -:warning: **We will not merge the PR to the main repo if your changes are not in a feature branch of your forked repository** :warning: +:warning: **We will not merge the PR to the main repo if your changes are not in a feature branch of your forked repository. Create a new branch in your repo, do not use the main branch in your repo!** :warning: Once the PR is created and submitted, we will be able to see the associated PR issue and will assist and provide feedback if necessary.