How Can I select some of my commits to pull requests?

[deepblue-knight]

Select Topic Area

Question

Body

Hi guys
I am new comer to Github, and did not do Pull Request before.
I have commited a few times on the projects, now I want to contribute my codes.
There are about 7 commits based on different fixing/improvement need to be contributed, so there are many changes on the codes, and maybe some files were updated for multiple times.Simply , the accumulated changes on the codes become complex,but I didn't create the branches for these commits, they are all on my main branch.
So I want to raise multiple pull requests according to the different updates, and there are some other commits are useless and should be excluded ,or it will be too hard for auditing if I include all of them in one pull request.
But when I try to new pull request, I find I cannot select my commits according to my needs.
Could you tell me if the website support such feature?below screenshot is just an example

[ronaldotantra]

To create multiple pull requests (PRs) from specific commits on your main branch, you’ll need to restructure your commit history using Git. This process involves creating new branches and cherry-picking the desired commits. Here’s a step-by-step guide: 

1. Create a New Branch from the Upstream Main Branch:

• First, ensure your local repository is up to date with the upstream repository (the original project repository).
• Create a new branch based on the upstream main branch:

git fetch upstream
git checkout -b new-feature-branch upstream/main

• Replace new-feature-branch with a descriptive name for your feature or fix.

2. Cherry-Pick Desired Commits:

• Identify the commit hashes of the changes you want to include in this PR.
• Cherry-pick each commit into your new branch:

git cherry-pick <commit-hash>

• Repeat this for each commit you want to include.

3. Resolve Any Conflicts:

• If you encounter conflicts during cherry-picking, Git will pause and allow you to resolve them.
• After resolving conflicts, continue the cherry-pick process:

git add <resolved-files>
git cherry-pick --continue

4. Push the New Branch to Your Fork:

• Push the new branch to your forked repository on GitHub:

git push origin new-feature-branch

5. Create a Pull Request:

• On GitHub, navigate to your forked repository.
• You should see a prompt to create a pull request for the recently pushed branch.
• Follow the instructions to open a new PR targeting the upstream repository’s main branch.

6. Repeat for Other Sets of Commits:

• For other features or fixes, repeat the above steps:
• Create a new branch from upstream/main.
• Cherry-pick the relevant commits.
• Push the branch to your fork.
• Open a new PR.

Important Considerations:

• Avoid Working Directly on the Main Branch: It’s a good practice to create a new branch for each feature or fix. This approach keeps your main branch clean and makes it easier to manage multiple PRs.
• Keep Your Fork Updated: Regularly sync your fork with the upstream repository to minimize conflicts and ensure you’re working with the latest code.
• Understand Cherry-Picking: Cherry-picking allows you to apply specific commits from one branch to another. It’s useful for selecting particular changes without merging entire branches.

By following this workflow, you can create focused and manageable pull requests, making it easier for maintainers to review and merge your contributions.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬