title: What are the best practices for tagging Docker Hub versions
body: <p>I have a Docker Hub container that runs an application. Normally it will run the application by cloning the source git repo but in the case that I'd like to run a specific version, the application has tagged various releases. For example I can do a </p>
  
  <pre><code>git clone https://github.com/author/application.git
  git checkout release-1.0.0
  </code></pre>
  
  <p>As the Docker Hub maintainer, I'd like to mirror the releases of the software with the container. Are there any other options besides just manually doing it when a release comes out?</p>
  
  <p>Right now my Dockerfile contains something like this:</p>
  
  <pre><code>ENV APP_VER=2.0.0
  RUN git clone ...; git checkout ${APP_VER}
  </code></pre>
  
  <p>In this example, I would keep a tagged branch of a docker file that sets the APP_VER to 2.1.0 and then Docker Hub supports that, but if I make changes to the repo, it's not clear how I would not make changes to that Dockerfile of each branch. </p>