summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFlorian Zschocke <f.zschocke+git@gmail.com>2025-06-14 19:08:49 +0200
committerFlorian Zschocke <f.zschocke+git@gmail.com>2025-06-14 17:20:54 +0000
commit22f4aea663df9887b5596c693fb00b86252d8654 (patch)
treea3acec1287d0a42aa372eda9978aa438c01ae76e
parentaaab003f600ec2815ea15e93a89681a344ecf0b4 (diff)
downloadgitblit-22f4aea663df9887b5596c693fb00b86252d8654.tar.gz
gitblit-22f4aea663df9887b5596c693fb00b86252d8654.zip
doc: Use www.gitblit.com in link to full release notesv1.10.0
The release process generates a release on Github. The release notes on Github link to the full release notes on the Gitblit website. But since gitblit.com/ only has a simple redirect in the index.html to the Github pages site, a direct link to the releasenotes on gitblit.com will end up in the outdated pages on Jame's site. Therefore use www.gitblit.com/ for the link, which we can control and which leads to the Github pages directly.
-rwxr-xr-xsrc/site/templates/ghreleasenotes.awk2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/site/templates/ghreleasenotes.awk b/src/site/templates/ghreleasenotes.awk
index f4479552..455334a1 100755
--- a/src/site/templates/ghreleasenotes.awk
+++ b/src/site/templates/ghreleasenotes.awk
@@ -6,7 +6,7 @@ BEGIN { on=0 ; skip=1 ; block=0 ; section=""}
/r[0-9]+: *{/ { on=1 ; next }
/^[[:blank:]]*}[[:blank:]]*$/ { if (on) {
- print "[Full release notes on gitblit.com](http://gitblit.com/releases.html#" relId ")"
+ print "[Full release notes on gitblit.com](http://www.gitblit.com/releases.html#" relId ")"
exit 0
}
}