Fork missing from Comparison List

[mjbear]

Select Topic Area

Question

Body

Is there a rhyme or reason as to which forks show up in a project's Comparison List?

(My GH discussions searches did not yield results that match what I'm encountering or trying to accomplish.)

There's a PR on a project, but there are some tweaks I'd like to submit to the original PR submitter.
Essentially I would like to submit changes to another person that forked the same upstream project so we can co-author a PR rather than submit multiple PRs.

I'm locally developing.
I (locally) added their fork as a remote, fetched their branches, switched to their branch, and made changes+commits. I pushed my new branch to my fork and went to the Pull Requests page to start a new PR against their fork so my PR is against that person's fork and not the main project (which would cause a second upstream PR).

I've ran into this problem before, but managed to try a few times and eventually a person's fork (for a different project) showed up.

Thank you for the assistance!

[eagle-provision]

When working with forks and pull requests (PRs) on GitHub, particularly when you want to collaborate with someone else's fork of a project, there are a few key points to keep in mind regarding the visibility of forks in the comparison list and submitting PRs.

Understanding Forks and PRs

1. Forks and Upstream Projects: Each fork of a project is essentially a clone of the original repository (upstream). When you fork a repository, you can make changes independently without affecting the original project.

2. Comparison List: The comparison list on GitHub typically shows branches from the same repository and any forks directly associated with that repository. If you're trying to compare branches across different forks, ensure that the base repository is correctly set to the fork you wish to contribute to.

Steps to Submit a PR to Another Fork

To successfully submit your changes as a PR to another person's fork, follow these steps:

1. Add the Fork as a Remote: You've already done this by adding their fork as a remote. You can check this with:

   git remote -v

2. Fetch Their Branches: Ensure you’ve fetched the latest changes from their fork:

   git fetch <remote-name>

3. Switch to Their Branch: Checkout the branch from their fork that you want to modify:

   git checkout <remote-name>/<branch-name>

4. Make Your Changes: After making your changes, commit them as you normally would:

   git add .
   git commit -m "Your commit message"

5. Push Your Changes to Your Fork: Push the changes to your own fork's branch:

   git push origin <your-branch-name>

6. Create a Pull Request:

   • Go to the GitHub page for the fork you want to contribute to.
   • Navigate to the "Pull Requests" tab.
   • Click "New Pull Request."
   • On the comparison page, select the base fork (the other person's fork) and the branch you want to merge into (typically the main branch of their fork).
   • For the head fork, select your fork and the branch with your changes.

Troubleshooting Visibility Issues

If the other person's fork isn't showing up in the comparison:

• Ensure Correct Base Repository: Make sure that the base repository for the PR is set to the person's fork, not the original upstream repository.
• Check Branch Names: Verify that you are comparing the correct branches. Sometimes, branch names may not match or may not exist in the target fork.
• Visibility Settings: Occasionally, repository settings or permissions can affect visibility. Ensure that the repository is public or that you have access to it if it's private.
• Refresh the Page: Sometimes, GitHub may not refresh immediately. Try refreshing the PR page or logging out and back in.

Collaboration Tips

• Communicate with the Original PR Submitter: If possible, reach out to the original author of the PR to let them know about your intended changes. This can help streamline your collaboration.
• Consider Creating a Feature Branch: If you plan to make extensive changes, consider creating a new feature branch in your fork for clarity.

By following these steps and tips, you should be able to successfully collaborate with another person's fork on GitHub. If you encounter specific error messages or issues, feel free to provide more details for further assistance!

[mjbear]

Ok. I've done all of this already.
I had already dropped a note to the PR submitter as well.