Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

site: set fallback version #80

Merged

Conversation

blocktrron
Copy link
Member

Add a fallback version, which is applied in case the site is built without tags fetched. This ensures the version string is not empty.

The fallback-version is set when branching a release off. It is et to the minor-version only. The patch version is omitted, like it is currently done for testing images.

Add a fallback version, which is applied in case the site is built
without tags fetched. This ensures the version string is not empty.

The fallback-version is set when branching a release off. It is et to
the minor-version only. The patch version is omitted, like it is
currently done for testing images.

Signed-off-by: David Bauer <[email protected]>
@herbetom
Copy link
Member

I think comparing and choosing the higher number could be useful. One might encounter a repo where some tags are present (for example those at the time of the fork) but not all. But as long as it's not empty the rest doesn't matter too much.

@blocktrron blocktrron merged commit 071eba4 into freifunk-darmstadt:master Jun 13, 2024
26 checks passed
@blocktrron blocktrron deleted the site-fallback-version branch June 13, 2024 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants