I am wanting to move our Altium files into git, currently there is a mixture of methods used for projects but essentially it boils down to a folder including the name and version, inside are the sch/pcb/prj files with the project name and version number, then another folder with the BOM, gerbers, another folder with things like step files that aren't already part of the components, eg case, etc.
How are others handling bumping revisions and file naming when using git?
I was initially thinking single repo per project then tag when released and bump the project parameter - the only thing I'm not convinced about using this method is file naming - it's ok for things like schematic where there's a version/revision number in the document block but how do you go about including that in the file name for things like gerber files? In the past I've named the project with the version number so you end up with projectName_v01.gerberlayer type of naming, this may be a lack of familiarity with outjob files though.
I was playing around with a outjob file to try get a structure like this but didn't have much luck.
-project
--variant A
---files for variant A
--variant B
---files for variant B
If anyone can share their method for keeping files within git, how they're released (outjob), how variants and new revisions are handled it would be appreciated
![Smiley :)](https://www.eevblog.com/forum/Smileys/default/smiley.gif)
I have heard whispers of the mythical one button release and wondered if anyone has managed to achieve this and integrate git into the process.