Git release branch management

Question

So, I first used git, and there is a script that I don’t quite know how to solve.

I have a simple webapp (html, css and js only) and I want to create regular releases that can be tracked with the version number. It is easy to do with git tag. But the trick is that for my releases I want to do some additional things, like js mini scripts and html page updates to point to them. Also, I need the .gitattute attribute in the release, which ignores non-minified js scripts, so that git archiveproduces the smallest possible output.

What I did creates a branch releases. This thread includes the aforementioned .gitattributesand modified html pages. Every time I want to get a new version, I switch to this branch, combining the changes with the wizard, then finish the release and put it in the version number. It seems to work the way I want, but I'm not sure how this should be done.

My question for more experienced git users is how is this case usually handled?

Answer 1

The branch solution is good, but for release management you can also just save the “release” in an external repository (for example, Maven or another Git repository declared as a submodule)

:

• ( )
• , "", -js.

( ) , , ( ).
, : .