simple, concise and clear. thanks raghav. i've one question if we cloned the repo so can we create a pull request to make our changes to the original remote repo?
Arif Certainly! When you clone a repository, you create a local copy of the project on your machine. To contribute changes back to the original remote repository (usually hosted on GitHub), follow these steps: 1. Fork the Repository: - First, fork the original repository on GitHub. This creates a copy of the repository under your GitHub account. - You can do this by clicking the "Fork" button on the original repository's page. 2. Clone Your Forked Repository Locally: - Use `git clone` to create a local copy of your forked repository on your machine: ``` git clone ``` - Replace `` with the actual URL of your forked repository. 3. Create a New Branch: - Navigate to the cloned repository using `cd `. - Create a new branch for your changes: ``` git checkout -b my-feature ``` - Replace `my-feature` with a descriptive branch name. 4. Make Your Changes: - Edit files, add new features, or fix issues in your local branch. 5. Commit Your Changes: - Use `git add .` to stage your changes. - Then commit the changes: ``` git commit -m "Description of your changes" ``` 6. Push Your Changes to Your Forked Repository: - Push your local branch to your forked repository on GitHub: ``` git push origin my-feature ``` 7. Create a Pull Request: - Visit your forked repository on GitHub. - Click the "Compare & pull request" button next to your branch. - Provide a brief description of your changes and click "Create pull request". - Your pull request will be submitted to the original repository for review. 8. Review and Merge: - The repository owner or maintainers will review your changes. - If everything looks good, they can merge your pull request into the original repository. Remember that you need to fork the repository first to create a pull request. Cloning alone won't allow you to directly submit changes to the original repository. ..
hi, #askRaghav Thanks for the very clear explanation with examples. I have 1 clarification if I add one more change(second change) after PR(first change) is closed, and raise PR again then it contains the changes of both the first change and the second change. So how do we refresh/re-fork the repo again without deleting this fork? so that PR can have only the changes which I have added in the second time
Hi Anu, once you have created a fork, you get the copy of the project, Now its on you what all changes you like to do and push it back to the repo. In your case, if you raise PR 2nd time and the first PR is already added and closed, the 2nd PR will contain the earlier changes
irrespective of what i do, fork or clone... in the end to get it merged in the original master created by author, I need to generate a pull request. Right?
Hi Anup, Yes, it is like downloading a folder to your system, so it will consume space. The amount of space consumed depends on the size of the repository, including its files, commit history, and any additional branches or tags
Hi, Deleting a private repository will delete all of its forks. Deleting a public repository will not delete its forks. Pls check this stackoverflow.com/questions/53052745/what-happens-to-the-forks-when-deleting-the-original-repository docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
Can check this stefanbauer.me/articles/how-to-keep-your-git-fork-up-to-date docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork
Thank You So So Much Sir🙏🙏🙏🙏
Most welcome Vaibhav
Very simple way of explaining things. Great!
Glad it was helpful
I could easily understood difference, thanks for such great video and putting your time in making and sharing video #mrnams
Very good. Thank you. Love from Germany :-)
Thanks Artur
Thanks Raghav! It was really helpful!
Most welcome!
yes. Its very good explanation sir.. Thank you so much..
Most welcome Manish
Again explained in easy, simple, short way. Live demo make me more clear now🎉🎉
Glad to hear that!
Awesome video. thanks for the clear explanation.
Most welcome
Like to Dislike Ratio in this video = Infinite .
My respect for Raghav Sir = Infinite .
Thanks a lot Siddharth
explained very nicely.Thank you so much
Most welcome
this is a superb and excellent video!
Thank you very much!
simple, concise and clear. thanks raghav. i've one question if we cloned the repo so can we create a pull request to make our changes to the original remote repo?
Arif
Certainly! When you clone a repository, you create a local copy of the project on your machine. To contribute changes back to the original remote repository (usually hosted on GitHub), follow these steps:
1. Fork the Repository:
- First, fork the original repository on GitHub. This creates a copy of the repository under your GitHub account.
- You can do this by clicking the "Fork" button on the original repository's page.
2. Clone Your Forked Repository Locally:
- Use `git clone` to create a local copy of your forked repository on your machine:
```
git clone
```
- Replace `` with the actual URL of your forked repository.
3. Create a New Branch:
- Navigate to the cloned repository using `cd `.
- Create a new branch for your changes:
```
git checkout -b my-feature
```
- Replace `my-feature` with a descriptive branch name.
4. Make Your Changes:
- Edit files, add new features, or fix issues in your local branch.
5. Commit Your Changes:
- Use `git add .` to stage your changes.
- Then commit the changes:
```
git commit -m "Description of your changes"
```
6. Push Your Changes to Your Forked Repository:
- Push your local branch to your forked repository on GitHub:
```
git push origin my-feature
```
7. Create a Pull Request:
- Visit your forked repository on GitHub.
- Click the "Compare & pull request" button next to your branch.
- Provide a brief description of your changes and click "Create pull request".
- Your pull request will be submitted to the original repository for review.
8. Review and Merge:
- The repository owner or maintainers will review your changes.
- If everything looks good, they can merge your pull request into the original repository.
Remember that you need to fork the repository first to create a pull request. Cloning alone won't allow you to directly submit changes to the original repository.
..
@@RaghavPal that's a satisfactory answer. i'm really thankful for your reply and your answer to my question. thanks again...
You have explained this thing in a very simple way🙌🫡
Thanks Abhishek
Your vids are a great resource sir. Keep going - More power to you.
So nice of you Raj
Thanks Raghav! Very useful. So it means if you clone without forking you can not contribute to the project, right?
Yes, correct Hamid
Thanks for your response. I wonder if you have tutorial for rebase in git?
Hi Hamid, can check this - ruclips.net/video/KWAZl2QHC44/видео.html
But we can create a branch in ORIGINAL repo and CLONE locally and create a PR to contribute too right?
very helpful. nicely explained.
Glad it was helpful!
great explanation. thank you!
Most welcome Caio
great explanation. thanks a lot man
You're welcome Piyush
much needed , thanks
You're welcome Ashish
Great video thank you.
Most welcome Akshay
Thanks for clarity
Most welcome Avtar
nicely explained!!!!!!!
Glad it was helpful
thanks for the video
You're welcome
Nice Explanation raghav
Glad you liked it Tulasi
hi, #askRaghav Thanks for the very clear explanation with examples. I have 1 clarification if I add one more change(second change) after PR(first change) is closed, and raise PR again then it contains the changes of both the first change and the second change. So how do we refresh/re-fork the repo again without deleting this fork? so that PR can have only the changes which I have added in the second time
Hi Anu, once you have created a fork, you get the copy of the project, Now its on you what all changes you like to do and push it back to the repo. In your case, if you raise PR 2nd time and the first PR is already added and closed, the 2nd PR will contain the earlier changes
irrespective of what i do, fork or clone...
in the end to get it merged in the original master created by author, I need to generate a pull request. Right?
Yes, can try with that Sourabh
hi sir when we pull from git hub to local machine will it consume space
Hi Anup,
Yes, it is like downloading a folder to your system, so it will consume space.
The amount of space consumed depends on the size of the repository, including its files, commit history, and any additional branches or tags
Thanks sir
Most Welcome Mohil
Made understanding Simple
Thanks for watching Vamsi
Hi #askRaghav If we delete original repo, does fork gets deleted too?
Hi,
Deleting a private repository will delete all of its forks.
Deleting a public repository will not delete its forks.
Pls check this
stackoverflow.com/questions/53052745/what-happens-to-the-forks-when-deleting-the-original-repository
docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
Does this work only for PUBLIC repo?
Public, or repo where you are added and have access
How to un fork any public repository
Tell about it.
This will help ralphjsmit.com/unfork-github-repo
Merge request and pull request is same?
No Usha, can also see some online examples
@@RaghavPal Okay,thanks for the quick reply.
how to keep in sync from orinal branch to fork branch
Can check this
stefanbauer.me/articles/how-to-keep-your-git-fork-up-to-date
docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork
Searched for cloning but got pull request for free😊😊😊😊
ok
👍
:)
Thanks for the clear explanation. So greatful
You're very welcome Amal