So, to be honest, right now I'm "playing" with each one to see how difficult it is to transition. Yet, it can be more inefficient because you need to use a different workflow than you are used to using on larger projects. If you use the same workflow for everything, it can be total overkill when you have a project that has a single developer. That said, I am debating with myself on the workflow between the following two things: ease of use for a particular project vs using a familiar workflow for all projects. Are you doing the same? I will outline the workflow I have been following (essentially the gitflow built in to SourceTree), which may be complete overkill for small projects, but I also think it will work well for large projects. So, I have been using the same tools, and pushing everything out to bitbucket. Comments on this, LAVA folks? Does anyone merge LabVIEW code routinely? My guess is that it wouldn't require all that much additional effort to make this a really useful tool (I think what is there is really pretty cool!), but with the current interface, it is rather useless in practice, and I can't remember ever using it to accomplish any meaningful merge task. I'm glad it exists, but I wish it would do more. *I think the merge functionality itself is pretty good, but the API-how it links to the version control provider-is lacking, in that it doesn't cover some very common use cases (I've written an ad hoc wrapper to trick it), and in that it can take a very long time to load the appropriate files sometimes. Comments on this, LAVA folks? Does anyone merge LabVIEW code routinely? Edited Novemby PaulL I would include the links if I could, but since those are disabled at the moment, you will have to do a search. I highly recommend taking a look at that. This workflow seems to be a logical, manageable, and consistent approach to handling development in branches and versioning (and seems to be applicable to LabVIEW, with the caveat that I recommend avoiding merging in LabVIEW with the present tools*). I was quite impressed with the Gitflow Workflow section, and I hope to implement that approach (I haven't gotten that far just yet) in the near future. (The use of the Pageant client is a bit clunky, but not really a problem.)Īnyway, Atlassian's Git Tutorials are quite good, and include some helpful sections on workflows. I've been using the Atlassian SourceTree client (free Windows and Mac-no Linux support at this time) and the more I use it, the more I like it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |