Let branch/tag name be a valid ref to get CI status #16400
Labels
No Label
backport/done
backport/v1.0
backport/v1.1
backport/v1.10
backport/v1.11
backport/v1.12
backport/v1.13
backport/v1.14
backport/v1.15
backport/v1.2
backport/v1.3
backport/v1.4
backport/v1.5
backport/v1.6
backport/v1.7
backport/v1.8
backport/v1.9
bounty
changelog
dependencies
frontport/done
frontport/main
good first issue
Hacktoberfest
hacktoberfest-accepted
in progress
kind/api
kind/breaking
kind/bug
kind/build
kind/deployment
kind/deprecated
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/misc
kind/moderation
kind/package
kind/proposal
kind/question
kind/refactor
kind/regression
kind/security
kind/summary
kind/testing
kind/translation
kind/ui
kind/upstream-related
kind/usability
kind/ux
lgtm/done
lgtm/need 1
lgtm/need 2
performance/bigrepo
performance/cpu
performance/memory
performance/speed
priority/critical
priority/low
priority/maybe
priority/medium
proposal/rejected
reviewed/confirmed
reviewed/duplicate
reviewed/fixed
reviewed/invalid
reviewed/not-a-bug
reviewed/wontfix
skip-changelog
stale
status/blocked
status/needs-feedback
status/wip
theme/2fa
theme/authentication
theme/avatar
theme/backup-restore
theme/docker
theme/federation
theme/issues
theme/kanban
theme/markdown
theme/migration
theme/mobile
theme/pr
theme/signing
theme/sqlite
theme/timetracker
theme/webhook
theme/wiki
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: lunny/gitea#16400
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix_16384"
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?
fix #16384
should check if the ctx.Repo.GitRepo is set and if so use that
@ -0,0 +2,4 @@
// Use of this source code is governed by a MIT-style
// license that can be found in the LICENSE file.
package utils
As lunny worried utils is becoming a bit of a catch-all package. Not necessarily this PR but I wonder if we these would be better in a git package.
@ -0,0 +19,4 @@
}
// Search branches and tags
for _, refType := range []string{"heads", "tags"} {
Now a branch named deadbeef will override the sha deadbeef. I'm not sure if that's completely intentional, it may be best to provide some marker or mechanism to force sha over branches/tags
@ -0,0 +19,4 @@
}
// Search branches and tags
for _, refType := range []string{"heads", "tags"} {
well this is how it works now for statuses and changing it would be to much for this bugfix
@ -0,0 +2,4 @@
// Use of this source code is governed by a MIT-style
// license that can be found in the LICENSE file.
package utils
will create an issue, this is a bugfix not a whole refactor ... you can find more similar code (git ref -> sha lookup) all over different places and we should unify them
@ -0,0 +2,4 @@
// Use of this source code is governed by a MIT-style
// license that can be found in the LICENSE file.
package utils
-> #16411
@ -0,0 +19,4 @@
}
// Search branches and tags
for _, refType := range []string{"heads", "tags"} {
-> #16411
well it original did not work this way but will add this optimisation