Home/ Questions/Q 7785563
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T20:16:34+00:00

I’m new to git and github, so apologies for the newbie question. I’ve searched

  • 0

I’m new to git and github, so apologies for the newbie question. I’ve searched the documentation and haven’t been able to tell what I’m doing wrong, or even IF I’m doing it wrong…

I’ve forked a repo on github, cloned it locally, made some changes in a couple of branches, committed those changes locally, and pushed them to my forked repo on github. While I’ve been working on that stuff, a variety of commits were made to the upstream repo I forked from. I’m not sure if this is the right thing to do, but I fetched and merged those upstream changes, then pushed again to my fork.

Now, I want to send a pull request to the upstream repo. But when I start to do that, github lists all the commits that would be part of the pull request, and it includes all those changes that were already made to the upstream repo that I fetched and merged already.

That doesn’t seem right. What do I need to do here?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is OK as you have pushed these commits to your forked repo and hence they logically belong to your pull request.

    When the pull request is merged by the upstream repo’s owner, Git will detect that it already “contains” some of the commits and will only merge in your changes.

    Just create your pull request and you are fine.

    • 0