Milestone Functions accept name to identify #388
No reviewers
Labels
No Label
has/backport
has/pull
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/go-sdk#388
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "6543:GetMilestones_add-name-to-id-resove-function"
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?
close #383
This LGTM, but I think we should start to move to different error types instead of just comparing error strings (this isn't a blocker though for this PR)
@techknowlogick #361 was ment to fix it but it looks like I have to submit my own one
@ -134,0 +164,4 @@
i := 0
for {
i++
miles, err := c.ListRepoMilestones(owner, repo, ListMilestoneOption{
This is really low efficient.
@lunny only on old instances - but I'm thinking we should do something similar for milestones as we did for tokens with https://github.com/go-gitea/gitea/pull/12366
while waiting for things ... exract update to #393
-> https://github.com/go-gitea/gitea/pull/12649
I think we should keep the resolve function for backwards (gitea <= 1.12) compatibilety but unexposed
blocked by https://github.com/go-gitea/gitea/pull/12649
@techknowlogick created new pull because this one is a mess now ... and
gitea currently dont work with forcepush to pull
-> #418
Pull request closed