Now auto complete behaves completely differently. I recently, too-trustingly, upgraded my Sublime Text 3 to Version 4 (Build 4107). I'm totally unaware of how things work in production, and I'm also not confident about my git knowledge, so sorry if this question seems naive or whatsoever. I just want to make sure if this is how "multiple versions with same code-base" projects are handled generally? If not, how is it commonly done? (A simple link or keyword to what I should look into would be helpful enough) This works fine on normal features, but when there is a minor bug (say, a typo) on the main branch, having to go over all these every time just so that the patched code could get to the client branches just seem kind of awkward and. Rebase client_a_branch and client_b_branch on main.Create branch new_feature_branch from main. Now I have a new feature that I want to work on, which applies to both A and B. These branches often have client-specific changes. A wants a blue theme and B wants a green one, so currently I just have them on two separate branches. Say I have a project (one code base) that is for two clients A and B. My macro-question is: Much like IntelliJ maintains dozens of IDEs that have almost the same basic functionalities but are built into different versions, is there some specific VCS tactic or best practices for doing so? I guess it's my git workflow that is mistaken, but I need some heads up on what I'm doing wrong. Nerd Fonts Patcher v3.0.2 (4.4.I'm currently working on a (laravel) project that should result in two versions, but I find myself constantly rebasing and merging my code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |