Haath Posted November 9, 2016 Share Posted November 9, 2016 Ok so basically what I want to know is, let's say that when Intersect goes open source I clone it and make a bunch of changes. When Intersect gets updated is it possible for me to get the update while also keeping the changes that I have made on my end? If so how do conflicts get resolved in that case? Does it only depend on how smart and modular the code I've added is?  I don't need some big explanation on how git works in general, just this piece of information if possible Thanks in advance! Link to comment Share on other sites More sharing options...
jcsnider Posted November 9, 2016 Share Posted November 9, 2016 Yeah so basically you will be able to hit a button to make a copy of Intersect in your own github account/workspace. You can then make changes. Â When I make changes to the main Intersect project you can pull those changes into your own workspace whenever you'd like. Â In the event of there being conflicts (both of us editing the same code) GitHub will tell you, and will add both your version and ours to the file. You can then open the file with a text editor and choose which version you want, or manually merge the two based on what you need. Â That is a really basic way of describing it. Merge conflicts can be tricky but we can help you work through them when they show up. Link to comment Share on other sites More sharing options...
Oddly Posted November 9, 2016 Share Posted November 9, 2016 What your asking is a question about subversion management and git repositories. I recommend looking up what a git merge is and what method conflicts are. You'll learn a lot about subversions Link to comment Share on other sites More sharing options...
Haath Posted November 9, 2016 Author Share Posted November 9, 2016 Ok thank you  And is there any way to get the pull to ignore specific files? For example if i've re-written an existing class and don't want to deal with conflicts on that  Link to comment Share on other sites More sharing options...
jcsnider Posted November 9, 2016 Share Posted November 9, 2016 Probably but at that point you are already going beyond my Git knowledge. Tons of guides/tutorials available to get you started though.  (and PS Git goes both ways.. if you make a change you want us to have you can send that change to us via Git (it's called a pull request) -- we can then evaluate your contribution and choose whether or not to add that to Intersect or not  ) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now