-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
[concept] Rationale for Github pull request #67
Comments
Findings
|
Addressing merge conflicts in pull requestTypes of merge conflicts
About merge conflicts
Resolving a merge conflict on GitHub
Resolving a merge conflict using the command line
|
Merging a pull requestAnyone with push access to the repo can complete the merge. If the pull request does not have any merge conflicts, you can merge it on Github. If the pull request does have merge conflicts, or if you'd like to rest the changes before merging, you can check out the pull request locally and merge it using the command line. If you decide you don't want the changes in a topic branch to be merged to the upstream branch, you can close the pull request without merging. Checking out pull requests locally
Modifying an inactive pull request locally
With issueID/ pull request ID, anyone can recreate all commits inside belonging to the issue/pull request
Details of Pull Request #60:
|
Merging a pull request on GitHub
Merge all of the commits into the base branch
Squash and merge your pull request commits
Rebase and merge your pull request commits
|
Comparing commits across time (Compare View)
Comparing branches
Comparing tags
Comparing commits
Comparing across forks
Comparisons across time
Comparisons across commits
Here's an example of a comparison using the ^ notation. |
By default, can original repo's owner push to fork (both public)?Answer:
Here are the details:1. Original repo's colalborators can propose commits to the fork, all commits they proposed will go via pull requests2. Then transferring to the compare view (comparing the patch branch on original repo and the branch you want to commit to of the fork repo3. All commits will be made in the committer's own repo (original repo in this testcase), via checking out a new patch branch |
Create a pull request
Changing the branch range and destination repository
Pull request from a fork
Collaborating with issues and pull requests
Creating a pull request from a fork
Defining the mergeability of pull requests
The text was updated successfully, but these errors were encountered: