Priorize groups by order #61
Labels
No Label
breaking
bug
build
duplicate
enhancement
feature
help wanted
invalid
lgtm
done
lgtm
need 1
question
skip-changelog
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/changelog#61
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?
at the moment a simple map[] is used, we should see the group list as priorized list since you can have lable overlap.
at the moment we could call it "unpredicted" behaviour!!!
https://github.com/go-gitea/gitea/pull/20023#issuecomment-1159518632
I have checked the code,
Group
is a slice andPR
is also a slice which could be sort. I don't know what did you meana simple map[] is used
.https://gitea.com/gitea/changelog/src/branch/master/cmd/generate.go#L24
https://gitea.com/gitea/changelog/src/branch/master/cmd/generate.go#L106-L108
we need am more inteligent function ...
A map is used, however the issue is not the map, but that the PR labels are only looped until first match.
The original idea was that labels wouldn't be overlapping.
A fix may be as simple as ordering PR labels by weight prior to looping.
i would not weight labels but see the order of group as priority
so if
and a pull has both labels, it is in the feature group