Skip to content

Add more guidance on creating feature branches #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 10, 2021
Merged

Add more guidance on creating feature branches #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Create-and-Submit-PullRequest.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down