If working in VS Code, does forking even make sense? #185
-
|
Hi everyone, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
It's still recommended to fork, as even though you are working in VS Code you are still working with a repository, and when you want to contribute back to something it's better to fork it in your own account, create your branch for the fixes or features you want to add within that fork, do what you need to do and then after committing your changes in that branch, make a pull request to merge those changes back to the parent. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @alexecution this is helpful. I think one way of looking at it is that by forking, I can create my own branches from within my forked version where as I might not be able to do that on a repository, either because rules might prevent it or because things would just get a bit crazy with a bunch of people creating a bunch of their own branches. I'm sure there are other advantages as well, but is my understanding correct at least where branches are concerned? |
Beta Was this translation helpful? Give feedback.
It's still recommended to fork, as even though you are working in VS Code you are still working with a repository, and when you want to contribute back to something it's better to fork it in your own account, create your branch for the fixes or features you want to add within that fork, do what you need to do and then after committing your changes in that branch, make a pull request to merge those changes back to the parent.