Bugfix: Set project field via api#37188
Closed
bircni wants to merge 3 commits intogo-gitea:mainfrom
Closed
Conversation
GiteaBot
added
the
lgtm/need 2
Contributor
|
Maybe it's better to focus on "multiple projects support for issue and pull requests", make the design stable first, otherwise there will be breaking API changes. |
Member
Author
The longer I think about it - yes! |
Contributor
#12974 and related PRs |
Contributor
|
It seems that the API has been implemented by Allow multiple projects per issue and pull requests #36784 Does this PR still have other improvements? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When creating or editing an issue via API, you can't set the Project field.
Fixes #37149