DEV Community

Cover image for Git and Managing Different Versions of the Same Application Question

Git and Managing Different Versions of the Same Application Question

Jack Harner πŸš€ on August 27, 2018

I'm working on a Chrome/Firefox extension. I started building it when I was using Chrome. I have since started using Firefox more. The extension is...
Collapse
 
ben profile image
Ben Halpern

I'm not confident enough to answer this, but I'm subscribed to the thread because I might have follow-up questions.

But...

Am I Dumb And Lazy or is This a Valid Way to Handle Separate Versions of the Same Thing?

I find the answer to this type of question is very often "yes, that's valid".

Collapse
 
jackharner profile image
Jack Harner πŸš€

I guess it does kind of fall into the category of "if it's dumb but it works, it's not dumb". I'm just curious to see what other ways people are solving this problem.

Collapse
 
skittishsloth profile image
Matthew Cory

I wouldn't say dumb, and lazy isn't a bad thing :) But personally - and I focus more on code than git usage so I'm biased - I would try and do something with the build and module structure.

Pretty sure you aren't using gradle or maven, but if I were doing this as a Java project I would structure it with a common library module, a module for chrome, and a module for firefox. Have the build script generate the appropriate artifacts and keep the git setup as simple as possible.