![]() We call the hari/repo the Forked Repository. The repository is now available in Hari's GitHub account as /hari/repo.We call the /tom/repo repository the Upstream Repository. So how does it work? Let's understand the workflow in steps. This second approach of forking a repository directly is more convenient for any contributor. He doesn't have to wait to talk to Tom and get Tom to add him as a contributor specifically. The second way is if Hari just forks the repo himself and starts working.As the project is already available as a public repository, he may just ask to fork it and use it. Could you please add me as a Contributor?". Hari asks Tom, "Hey Tom, I want to contribute to your project.Now there are two ways Hari can approach it. Hari is amazed by the idea and wants to contribute to the project. Tom is working on an outstanding project, and he manages its source code in a public repository called /tom/repo. Tom and Hari are two developers who have their individual GitHub accounts. So, let's understand the entire forking workflow with the story of two developers, Tom and Hari. ![]() ![]() They are most likely to take your code changes after approval. Once you get the local copy of the code, you can make the relevant changes and ask the React community to review your changes.Īfter reviewing your code changes, the React community may approve them or ask you for more changes. React's source code is available as a public repository on GitHub, so you can make a local copy of it by forking it. One fine day, you figure out a way that you can enhance the functionality of React yourself. Suppose you love working on a particular framework or library like React.js.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |