github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 12:46:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Proposal: Change purpose of docker labels on docker hub #1219

New Issue
Closed
opened 2025-11-02 03:52:49 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 03:52:49 -06:00
Owner
Copy Link

Originally created by @techknowlogick on GitHub (Nov 6, 2017).

Currently latest on docker hub uses the latest commit from the master branch. This proposal is to add an additional tag (something like dev, devel, or unstable) in place of that, and instead use latest as the latest stable version (at time of creating this repo it is 1.2.3).

Originally created by @techknowlogick on GitHub (Nov 6, 2017). Currently `latest` on docker hub uses the latest commit from the master branch. This proposal is to add an additional tag (something like `dev`, `devel`, or `unstable`) in place of that, and instead use `latest` as the latest stable version (at time of creating this repo it is 1.2.3).
GiteaMirror added the topic/deployment label 2025-11-02 03:52:49 -06:00
GiteaMirror commented 2025-11-02 03:52:50 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Nov 6, 2017):

Perhaps a first step is to create that second label on docker hub, and then change the purpose of latest. I'd be open to creating that PR.

@techknowlogick commented on GitHub (Nov 6, 2017): Perhaps a first step is to create that second label on docker hub, and then change the purpose of `latest`. I'd be open to creating that PR.
GiteaMirror commented 2025-11-02 03:52:50 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Nov 7, 2017):

Closing in favour of #2827

@techknowlogick commented on GitHub (Nov 7, 2017): Closing in favour of #2827
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/deployment
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1219
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?