Checkout branch vs checkout tag? #93
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/gitea-docusaurus#93
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.
Yes. Versions are all hard coding which seems not good.