#Find my forks on github desktop code#

At this point, GitHub forks the repository for you. Click the name of the file you want to edit.Ībove the file content, click. In another user's repository, browse to the folder that contains the file you want to edit. When you edit a file in another user's repository, we'll automatically fork the repository and open a pull request for you. For more information, see ' Creating a pull request.'Įditing files in another user's repository If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. For more information about the exact form the no-reply email address can take, see ' Setting your commit email address.'īelow the commit message fields, decide whether to add your commit to the current branch or to a new branch.

If you enabled email address privacy, then a no-reply will be the default commit author email address. Only verified email addresses appear in this drop-down menu. If you have more than one email address associated with your account on, click the email address drop-down menu and select the email address to use as the Git author email address. For more information, see ' Creating a commit with multiple authors.' You can attribute the commit to more than one author in the commit message. In the 'Commit message' field, type a short, meaningful commit message that describes the change you made to the file. Theres a 'fast-forward' button on your fork of the repository that you can use to catch. GitHub, in all its perpetual awesomeness, gives you a shortcut, of course. Merging should do the right thing with your commits on both branches. In the text box, make any changes you need to the file. You just need to fetch the list of commits from the other repository and then merge his branch into your tree. The fork can then stand on it’s own, or be merged back with the original repository. You can also clone the repository and edit the file locally via GitHub Desktop by clicking GitHub Desktop. Forks can be copied (cloned), then changed from the original repository.

#Find my forks on github desktop code#

Note: Instead of editing and committing the file using the default file editor, you can optionally choose to use the v code editor by selecting the dropdown menu and clicking v.