Fork and pull request | Git and GitHub | Tutorials | Projects | Motivation | Tamil |

Previous video links: 1. Git and GitHub introduction : https://youtu.be/UIM2xiTn-_Q 2. Git and GitHub setup, Local system commands : https://youtu.be/Eb-pSRAg2-0 3. Git remote and basics - https://youtu.be/l1bITUFXmqs 4. Git branching - https://youtu.be/x-sx1mfF3s8 5. Git merge and rebase - https://youtu.be/KCYs4G3FtDU 6. Git fork and pull request - https://youtu.be/0zCdNUHIcSY Chapters of this video: Introduction: 00:00 - 00:30 Motivation 1: 00:31 - 02:16 Motivation 2: 02:17 - 03:00 Fork: 03:01 - 04:25 Fork tutorial: 04:26 - 08:30 Pull requests: 08:31 - 09:37 Pull requests tutorial: 09:38 - 11:30 Project: 11:31 - 14:34 Summary: 14:35 - 14:42 Fork: Fork is used to create a server-side copy along with commit history. Forking a repository allows you to freely test and debug with changes without affecting the original project. One of the excessive use of forking is to propose changes for bug fixing. When to use git fork? Propose changes to someone else's project. Use an existing project as a starting point. Forking is not a git function; it is a feature of git service like GitHub. GitHub do not support creating forks from your own repository. Pull request: A contributor/developer is ready to begin the process of merging new code changes with the main project repository. During a pull request, the repository maintainer reviews new code updates from a developer to determine whether or not it is ready to be released. Once the repository maintainer has approved a pull request, the developer’s new updates in the forked repository are merged with the main project repository. External developer: Without fork – no pull request to original repository #git #gitfork #pullrequest #gittamil #github