Checkout branch vs checkout tag? #93

Open
opened 2023-11-27 02:57:32 +00:00 by yp05327 · 2 comments

We checkout branches for each version to generate the latest pages. But it does not match the version strictly.
For example, in the website it said this docs is for version 1.21.0. But actually it is for the next version 1.21.1,
as we directly backport changes into branch release/v1.21.

So how about using checkout tags for the released version, and using checkout branch for the latest patch version of each minor versions.

We checkout branches for each version to generate the latest pages. But it does not match the version strictly. For example, in the website it said this docs is for version 1.21.0. But actually it is for the next version 1.21.1, as we directly backport changes into branch `release/v1.21`. So how about using checkout tags for the released version, and using checkout branch for the latest patch version of each minor versions.
Owner

Maybe we can have some code change to detect the latest tag and change it automatically. With Gitea Actions, I think it's not too difficult.

Maybe we can have some code change to detect the latest tag and change it automatically. With Gitea Actions, I think it's not too difficult.
lunny added the
Kind/Enhancement
label 2023-11-27 07:09:38 +00:00
Author

Yes. Versions are all hard coding which seems not good.

Yes. Versions are all hard coding which seems not good.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/gitea-docusaurus#93
No description provided.