gitea

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

zeripath bc77b28d9d Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch (#18551 ) * Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch One of the problems with our current docker tagging is that although we have strict version tags, latest and dev we do not have a way for docker users to track the current release branch. This PR simply suggests that we use the 1.x-dev tag for these and we build and push these. This will give users who want or need unreleased bug fixes the option of tracking the pre-release version instead of simply jumping to dev. Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: KN4CK3R <admin@oldschoolhack.me> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	3 years ago
..
doc	Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch (#18551 )	3 years ago
page	Fix various typos of software names (#18083 )	3 years ago

zeripath bc77b28d9d

Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch (#18551 )

* Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch

One of the problems with our current docker tagging is that although we
have strict version tags, latest and dev we do not have a way for docker
users to track the current release branch. This PR simply suggests that
we use the 1.x-dev tag for these and we build and push these. This will
give users who want or need unreleased bug fixes the option of tracking
the pre-release version instead of simply jumping to dev.

Signed-off-by: Andrew Thornton <art27@cantab.net>
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>

doc

Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch (#18551 )

page

Fix various typos of software names (#18083 )