Fetch&rebase support for pull requests #56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Here's a commit that adds support for private repos to kohsuke's fetch-pull feature: |
Support for private repositories.
|
The change mentioned in the comment from nixon is now merged into this pull request. |
add merge, rebase and do-nothing options to the fetch-pull command. i like being able to fetch a pull request by number, but sometimes i'd rather not have the rebase happen automatically.
Fetch pull with options
Conflicts: .gitignore
There's a lot more work to be done to convert other calls, but this is a start.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I work on projects on GitHub that receives a fair number of pull requests, and most of the time I need to make some slight adjustments on them before merging changes. I also do fetch+rebase when merging pull requests in an attempt to create more linear history. I find it easier to comprehend what was going on that way.
To that end, I added a command to do this in one shot:
If you find this command useful, would you please consider merging it?