About README.md #148
-
|
Hello @kunalkeshan, Situation is when you merge PR which was created by me, I need to sync it again. No problem in syncing, but why that GitHub does one commit automatically, Why is it needed? The reason I am asking is that the next time I am going to contribute(opening PR), it shows What is the solution to this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
|
The only way is to keep in Sync with the main repo. The reason is that myself and others contribute as well. So it would be best if you considered the newly updated contributions along with the ones you made to ensure that your changes also work. |
Beta Was this translation helpful? Give feedback.
-
|
Means I need to re-fork every time! Right? |
Beta Was this translation helpful? Give feedback.
-
|
You just need to fork it once. And sync updates before contributing to the same repository. eg:
|
Beta Was this translation helpful? Give feedback.
-
|
If I sync the fork then GitHub will add an extra commit of Am I Right? (Actually, This is big confusion of mine) |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it will add the commit from the source repo. In the next contribution, creating a branch from your This allows you to avoid adding additional commits to the same branch, (because sometimes the repo maintainer might use squash and merge) and also make sure that you receive the same commits from the source repo for the |
Beta Was this translation helpful? Give feedback.
-
|
💬 Chat bubble I was thinking of adding Emoji before the So, Can I open PR with these changes?
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah Sure, feel free to do it. |
Beta Was this translation helpful? Give feedback.
-
Finally, Let's Goooooooooo>>>>🤩😇🎉🎊🎇🎆🏇🤾♂️⛷️🏄♀️🚄 |
Beta Was this translation helpful? Give feedback.
Yes, it will add the commit from the source repo. In the next contribution, creating a branch from your
mainrepo is best recommended and merging it into themainbranch of the source repo to avoid conflicts.This allows you to avoid adding additional commits to the same branch, (because sometimes the repo maintainer might use squash and merge) and also make sure that you receive the same commits from the source repo for the
mainbranch.