Skip to content

Improve clarity on comparing changes and Pull Requests #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chryzcode merged 1 commit into from
Oct 20, 2025
Merged

Improve clarity on comparing changes and Pull Requests #154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,11 @@ After the commit, then click the Pull Request tab and make new Pull Request
<img align="center" src="https://github.com/chryz-hub/opensource-4-everyone/blob/master/chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/pr-1-4.jpg" />

### 5. Comparing Changes
This is all about the comparison between your own forked version and the original repository to check if there are any changes and whether those changes are mergeable. You’ll see the phrase `comparing across forks` along with a transitional line that has an arrow in the middle. Make sure this is set correctly to avoid issues.

This is all about the comparism between your own forked version and the real repository to check if there was a change and if the change is mergeable. You can see the word `comparing across forks` and a transitional line with an arrow in the middle. You must set this well to avoid issue, now we are sending from mine to the main/real repository using the direction of the arrow, then you can make your Pull request. If it is not mergeable, you can still make the Pull Request and resolve it `resolve conflicts`, GitHub would point out the issue which makes it easier for you to resolve.
We’re now sending changes from your fork to the main (original) repository, following the direction of the arrow. After that, you can create your Pull Request.

If it isn’t mergeable, you can still make the Pull Request and then resolve the conflicts. GitHub will highlight the issues, making it easier for you to fix them.
<img align="center" src="https://github.com/chryz-hub/opensource-4-everyone/blob/master/chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/pr-2-5.jpg" />

### 6. Create Pull Request Message
Expand Down