github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Assign a specific branch for the issue being created when using API. #12721

New Issue
Closed
opened 2025-11-02 10:19:04 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 10:19:04 -06:00
Owner
Copy Link

Originally created by @maks-mishin on GitHub (Mar 24, 2024).

Feature Description

It became necessary to assign a specific branch for the issues being created when using the API.

It is possible to assign a branch to an issue when using the GUI (screenshot), but there is no such field when creating issues via the API.

Screenshots

Assign branch

Originally created by @maks-mishin on GitHub (Mar 24, 2024). ### Feature Description It became necessary to assign a specific branch for the issues being created when using the API. It is possible to assign a branch to an issue when using the GUI (screenshot), but there is no such field when creating issues via the API. ### Screenshots ![Assign branch](https://github.com/go-gitea/gitea/assets/24493995/eeb3ba08-48d3-4cf7-98ae-75fea0cd3a60)
GiteaMirror added the type/proposal label 2025-11-02 10:19:04 -06:00
GiteaMirror commented 2025-11-02 10:19:05 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 18, 2024):

This has been implemented https://docs.gitea.com/api/1.22/#tag/issue/operation/issueListIssues .

@lunny commented on GitHub (Sep 18, 2024): This has been implemented https://docs.gitea.com/api/1.22/#tag/issue/operation/issueListIssues .
GiteaMirror commented 2025-11-02 10:19:05 -06:00
Author
Owner
Copy Link

@maks-mishin commented on GitHub (Sep 18, 2024):

Thanks! Today I discovered this functionality and closed the issue.

@maks-mishin commented on GitHub (Sep 18, 2024): Thanks! Today I discovered this functionality and closed the issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12721
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?