Git repository. A repository for all files and folders of a project.
From github create new repository. Main branch is the copy with all changes have been “pulled”. A new branch, or feature, is where new things are added / modified. As you create/edit files in the branch, you need to commit them to the branch
Branches should have meaningful names
Changes in branches need to be “pulled”. A pull requests indicates changes are proposed for inclusion with the main branch.
Fork a repository to make a copy under your own user account.
Q: Does fork create a local copy on e: or just on github account repository?n Based on octocat/Fork-Knife, it does not create anything on E.
Q: So how to make E version
Create New Branch
From Github desktop, create new branch and publish it to github.com. Now any changes made in Visual Studio Code can be Push/Pulled to that version on Github. After fully tested, the branch should be merged into the Main branch.
Pull Request
...proposes that changes you've made on a branch should be merged into a base branch.
From Code,
Consider configuring all pull requests You can configure a pull request to merge automatically when all merge requirements are met. For more information, see "Automatically merging a pull request."
From repository, click Source Control icon, stage each change, Commit changes to branch.
Everything else can be done from Github Desktop. Push committed changes, Pull and Merge to Main.
- Click Pull request
- Compare main to branch
- Create Pull request with appropriate comments
- Merge pull requests
- Confirm Merge request
- "Pull request successfully merged and closed
From the GH desktop menu, click Branch, create new.
Publish it to remote.
It should now be available as an option in Visual Studio Code.