PR is indicated as failed but accepted at parent repository

[johnwslongland]

Select Topic Area

Question

Body

Hi
I have made a PR onto a public repository and it was accepted and merged. However, it been my first PR, I did not complete all the subjects as per standard and now the PR is indicated at my repository as failed. There for 1 commit ahead of upstream repository. And yet it was merged. I wish to make another PR but I fear that this seemingly "outstanding" PR is going to mess things up.

Steps taken to get more info..

1. On my respository it indicates : "This branch is [2 commits ahead of...."
2. I click on the message and it give me more info.... see attached snip1.png and snip2.png
3. It comes down to the fact that ( with it been my first PR ) I structured my commit command incorrectly
4. Fact is, PR was merged but my repository is still indicated as 2 commits ahead of upstream.

Not sure how to resolve this. Some guidance would be appreciated.

[justsarx]

It sounds like your fork is simply out of sync with the parent repository’s default branch, which is why GitHub is still showing a mismatch (“2 commits ahead, 1 behind,” or a “failed” status) even though your pull request was accepted and merged upstream. You can resolve this by updating (or “syncing”) your local repository and your fork on GitHub so they match the parent repository’s latest state. Here’s how you might do that:

1. Add the parent repository as an additional remote
   If you haven’t already, add the parent repository (the one where your PR was merged) to your local Git settings. For instance, if the parent repo is at https://github.com/example-org/example-repo.git, you can do:

git remote add upstream https://github.com/example-org/example-repo.git

Check which remotes you already have by running git remote -v.

2. Fetch and merge (or rebase) the latest upstream changes
   Make sure you’re on your local main (or master) branch:

git checkout main
git fetch upstream
git merge upstream/main

or use git rebase upstream/main if you prefer a linear history. This ensures your local environment is fully up to date with the parent project’s main branch.

3. Push changes back to your fork
   After merging or rebasing, push these updates to your fork on GitHub:

git push origin main

This way, your forked repository’s default branch reflects the latest commits from upstream. GitHub should then no longer show it as “behind” or “failed.”

4. Delete or clean up the old feature branch (optional)
   If your old feature/PR branch is no longer needed, you can safely delete it both locally and on your fork. For example:

git branch -d <feature-branch>
git push origin --delete <feature-branch>

Cleaning up old branches can prevent confusion later.

5. Create a new pull request when you are ready
   With your fork and local repo fully synced, any new PRs you open should start off with the correct “clean” status.

In most cases, GitHub doesn’t prevent you from opening new pull requests just because an old one has a “failed” badge in your fork; usually, it’s just a UI indication that your fork is behind. The key is to get your local and fork branches up to date with upstream so GitHub recognizes that everything has been merged properly. Once that’s done, you should be all set to open a fresh pull request if you still have changes you want to contribute.

[johnwslongland]

Thank you @justsarx , I have applied your posting and it seems everything is normal.

I now see only 1 commit ahead of upstream, which is what I am expecting as there is a PR in draft mode outstanding. I checked on this draft PR and all checks pass. So this time it seems I have my titles rights. So I have just requested a review , ie changed draft PR to full PR.

Appreciate your time.