SDK depends on Gitea #177
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/go-sdk#177
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?
Author: @jonasfranz
go-sdk depends currently on code.gitea.io/gitea that implicates that all dependencies of gitea are needed to for go-sdk. We should consider fixing this since it will increase the size of binaries of tools using the sdk.
Author: @lunny
In fact, it only depends
code.gitea.io/gitea/modules/structs
, butgo mod
will require all the packages of gitea. Maybe we should put go.mod oncode.gitea.io/gitea/modules/structs
to fix this problem?This cannot be resolved even if code.gitea.io/gitea/modules/structs becomes a module.
I think @jonasfranz is right. We have to fix this.
I propose to remove the dependency on
code.gitea.io/gitea/modules/structs
and copy all necessary structs from that packages.And we should create branches/tags to follow gitea's version so that we can avoid a compatible problem. That means when gitea create a new branch i.ie release/v1.10.
sdk
should also create a branch release/v1.10 to follow gitea's change. Then you could use different branch to operate different version Gitea.I sent a PR #188 to resolve this problem. Please review.
Closed by #188.