Updates and priority changes #62
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#62
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "jolheiser/changelog:priority"
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?
Closes #61
This PR does some general cleanup and implements pseudo-priority based on the order defined in the changelog config.
It makes use of the
embed
package and removes the workaround that was previously used for the default config.It updates
go.mod
togo 1.18
, but this shouldn't be a problem as changelog is mostly an internal tool.It also changes a few variables to be non-exported in order to better control their scope.
@ -15,7 +15,7 @@ steps:
pull: always
image: golang:1.17
1.18
@ -51,0 +44,4 @@
}
}
if defaultGroup == "" {
defaultGroup = cfg.Groups[len(cfg.Groups)-1].Name
should we just drop if there is no default group and no group match?
I'm ambivalent, but that would technically be a breaking change. This is how the old logic worked.
something for next pull ;)
I think we should break this but agree - this is out of scope for this pull
@ -1,24 +1,84 @@
// Copyright 2020 The Gitea Authors. All rights reserved.
intentional?!?
Ah, nope. I had deleted the file and then renamed a different one to this, but forgot a new copyright.
@ -27,3 +26,4 @@
$(GO) test -race -v ./...
.PHONY: lint
lint:
I think we should switch to use
go install ...
hereOr
go run
, now that Go supports versioned running@ -48,3 +38,3 @@
}
processPRs(prs, cfg.SkipRegex)
var defaultGroup string
Shouldn't these code be invoked before
service.New
?I dont see it in use before ... so more a code-convention thing when to init vars?
I'm ok as it's done atm by the way...
I always init the var right before I need it. In terms of
service.New
, the service is only responsible for getting entries, not for grouping them. That happens further down.