Geek asks and answers

Is the "Remote Tracking Association" xxx / master "" a problem for a Pull request?

There is a Github repository . I have forked on which there are several commits made subsequently.

I wanted these fixes to be part of my forked repository, I could merge them (but can't remember how), and now I have a commit named Merge remote tracking branch "blount / master" .

Is this a problem for future requests for requests? Or they will not have any cases when the owner accepts my request for traction?

I found Why am I combining the question of the origin / development of “remote branch tracking in development”? Stackoverflow, which says how to avoid this situation, but not if existing merges are a problem.

+3
source share
1 answer

It depends, generally speaking, on whether a) the pull request is automatically combined b) (more importantly), whether the tests pass.

You can create a remote upstreamthat points to the original repository, then merge upstream masterin origin masterand it will be updated.

You must do this first to proactively resolve any merge conflicts or unexpected breakdowns.

0
source

More articles:


All Articles