GitHub – How to Change Multiple Files and Submit in One Pull Request
github
I used GitHub's web interface to commit changes to multiple files. For each file, a new pull request has been created:
Does the web interface allow to merge multiple requests so that I can submit all changes in just one request?
Best Answer
If you don't want to think about branches, do the following:
Fork the repository using the Fork button.
Make your changes to your fork (there will be a commit for each file changed, made by default to the master branch).
When you're done, create a pull request using the button "Compare and pull request". The user will get one PR with several commits in it, which is not unusual. They will be able to review all changes at once.
If you want to think about branches... generally, one doesn't commit provisional changes directly to master branch, so that changes can be disregarded easily by deleting the branch. This is why GitHub automatically creates a branch such as patch-1 in your forked repository when you try to edit a file that you can't edit directly.
You can create a "patch" branch yourself, in the forked repository. Or you can take advantage of GitHub's automatic branching and keep the commits in one pull request as follows.
Make the first change by using the edit icon in another user's repository. This creates a fork of repository, and in it a branch such as patch-1. Do not create pull request yet.
Go to the list of repositories in your profile, go to the forked repository you've just made, and switch to patch-1 branch. Continue making changes. When you are done, click "Compare & pull request".
On the sidebar, under Notifications, you will be able to toggle your subscription to the thread.
You can also now manage notification settings at the individual issue or pull request level. This lets you manually subscribe to any issue without commenting, or unsubscribe from issues no longer relevant to your interests:
Github is going to use the first address listed in your Account Settings/Email Addresses.
Right now the only way I know to change the primary email address that is used, it to delete the email addresses above the one you want to use, then add them back after the email address you want to use is at the top.
Best Answer
If you don't want to think about branches, do the following:
Make your changes to your fork (there will be a commit for each file changed, made by default to the master branch).
When you're done, create a pull request using the button "Compare and pull request". The user will get one PR with several commits in it, which is not unusual. They will be able to review all changes at once.
If you want to think about branches... generally, one doesn't commit provisional changes directly to master branch, so that changes can be disregarded easily by deleting the branch. This is why GitHub automatically creates a branch such as patch-1 in your forked repository when you try to edit a file that you can't edit directly.
You can create a "patch" branch yourself, in the forked repository. Or you can take advantage of GitHub's automatic branching and keep the commits in one pull request as follows.