ignore PRs in runIssuesList() (fixes #108) #110
No reviewers
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Depends on
#285 add ListRepoIssues option for Issue Type
gitea/go-sdk
Reference: gitea/tea#110
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "noerw:issue-108/nopulls"
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?
fixes #108
Although I kinda think that this should this be solved at API level?
Seems unintuitive for
/api/issues
to also return pulls.The API does actually have a way to filter only issues, but it's not in the SDK currently.
See https://try.gitea.io/api/swagger#/issue/issueListIssues
type
@jolheiser good point!
@noerw go-sdk taged v0.11.1 so pleace update and you will have the option for issue types
@6543 Not sure what you did there, but v0.11.1 does not include
IssueType
:@noerw thanks you detect an error ... fixed the wrong tagging ... the wrong sha was tagged.
now it should work: https://gitea.com/gitea/go-sdk/src/tag/gitea/v0.11.1/gitea/issue.go#L51
Even after cleaning the go module cache, the old sha is still fetched by
make vendor
.. Maybe some proxy didn't update the sha on v0.11.1? Could we just skip v0.11.1 and tag v0.11.2?gitea/go-sdk#298
@noerw -> #111
created pull hope you dont mind :D
Pull request closed