2.4.0 Steps to reproduce the behavior Fork a repo. On user-owned forks, if you want to allow anyone with push access to the upstream repository to make changes to your pull request, select Allow edits from maintainers. Describe the bug When opening a repo forked from somewhere else, 'View on Github' will open the original repo instead of my forks URL.
The first step is to fork the GitHub repository you want to work on. Delete your feature branch using the GitHub website or, delete the local branch: git branch -d newfeature, and delete the remote: git push origin -delete newfeature. In the list of pull requests, navigate to the pull request that you'd like to allow commits on. Change to master: git checkout master and pull: git pull upstream master. Under the upstream repository name, click Pull requests. On GitHub, navigate to the main page of the upstream repository of your pull request. Enabling repository maintainer permissions on existing pull requests For more information, see " Creating a pull request from a fork." Additionally, you can modify an existing pull request to let repository maintainers make commits to your branch. You can set commit permissions when you first create a pull request from a fork. This precision just to avoid any confusions between clone and pull. For more information, see " Creating a pull request from a fork." Note that for a specific branch git clone is usually used once (unless you want to copy your project in others folders/branch) In your question the word 'pull' is important since it is also a git command (git pull) which will pull changes made in a remote repo. You can also click URL to manually enter the repository location. Click the tab that corresponds to the location of the repository you want to clone. In the File menu, click Clone Repository. You can select one commit or select multiple. In GitHub Desktop, if you attempt to clone a repository that you dont have write access to, a fork is automatically created for you. You can select one commit or select multiple commits using Command or Shift. Select the commit you would like to cherry-pick. Pull request authors can give these permissions when they initially create a pull request from a user-owned fork or after they create the pull request. In the list of branches, click the branch that has the commit that you want to cherry-pick. To learn more about upstream repositories, see " About forks." See which pull requests pass commit status checks, too Syntax.
Checkout branches with pull requests and view CI statuses See all open pull requests for your repositories and check them out as if they were a local branch, even if theyre from upstream branches or forks. If the pull request author wants greater collaboration, they can grant maintainers of the upstream repository (that is, anyone with push access to the upstream repository) permission to commit to the pull request's compare branch. Focus on what matters instead of fighting with Git. Pretty much any other client is better than GitHub Desktop (recommendations are Fork and then SourceTree from me, if you can use them, full disclaimer: GitKraken is probably great too, but I don’t have the experience with it to recommend it).When a user creates a pull request from a fork that they own, the user generally has the authority to decide if other users can commit to the pull request's compare branch.By all means use GitHub (the server) though that’s fabulous.viewing commit history of branches) and has been lacking other basic features like being able to delete a branch.īut not even being able to create a tag until now, which is basically just an adhoc label, is crazy. I do not even recommend GitHub Desktop for people who are new to git under the claim of “well if it has less features it is probably easier to get going / onboarded”, because its UI layout is also crooked (e.g. And of course from SourceTree, Fork, or whichever other poison you choose. In the 'base branch' dropdown menu, select the branch of the upstream repository. On the page to create a new pull request, click compare across forks. Above the list of files, in the yellow banner, click Compare & pull request to create a pull request for the associated branch. To check for commits on the remote branch, click Fetch origin. Navigate to the original repository where you created your fork. Thankfully you can do it direct from Visual Studio, which is actually a better git UI client than GitHub Desktop. In GitHub Desktop, use the Current Branch drop-down, and select the local branch you want to update. I mean seriously… this should have been in since day 1.