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

bug: cannot edit branch once issue was created #2624

New Issue
Closed
opened 2025-11-02 04:42:31 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-02 04:42:31 -06:00
Owner
Copy Link

Originally created by @mckaygerhard on GitHub (Dec 5, 2018).

  • Gitea version (or commit ref): 1.6.0
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

In issues cannot edit the branch associated once the issue was created!

Screenshots

canot-edit-associated-brand

Originally created by @mckaygerhard on GitHub (Dec 5, 2018). - Gitea version (or commit ref): 1.6.0 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description In issues cannot edit the branch associated once the issue was created! ## Screenshots ![canot-edit-associated-brand](https://user-images.githubusercontent.com/1571724/49517520-c59a8b00-f872-11e8-9a65-dacce3b36c1d.png)
GiteaMirror added the issue/confirmedtype/enhancement labels 2025-11-02 04:42:31 -06:00
GiteaMirror commented 2025-11-02 04:42:31 -06:00
Author
Owner
Copy Link

@Etzelia commented on GitHub (Dec 5, 2018):

I don't understand what "brand" you mean.
Are you referring to labels? If so, click the gear icon and remove the unwanted label from the dropdown.

Tested on https://try.gitea.io

@Etzelia commented on GitHub (Dec 5, 2018): I don't understand what "brand" you mean. Are you referring to labels? If so, click the gear icon and remove the unwanted label from the dropdown. Tested on https://try.gitea.io
GiteaMirror commented 2025-11-02 04:42:32 -06:00
Author
Owner
Copy Link

@mckaygerhard commented on GitHub (Dec 5, 2018):

@Etzelia do you see in image the "master" asociated branch? in the issue, once created i try to change the related associated branch and i cannot do it! pufff!

@mckaygerhard commented on GitHub (Dec 5, 2018): @Etzelia do you see in image the "master" asociated branch? in the issue, once created i try to change the related associated branch and i cannot do it! pufff!
GiteaMirror commented 2025-11-02 04:42:32 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Dec 6, 2018):

It is not bug, it is just way it is implemented

@lafriks commented on GitHub (Dec 6, 2018): It is not bug, it is just way it is implemented
GiteaMirror commented 2025-11-02 04:42:32 -06:00
Author
Owner
Copy Link

@mckaygerhard commented on GitHub (Dec 6, 2018):

umm ok so then we need a feature to edit/change if a user make misctake or get wrong branch right?

@mckaygerhard commented on GitHub (Dec 6, 2018): umm ok so then we need a feature to edit/change if a user make misctake or get wrong branch right?
GiteaMirror commented 2025-11-02 04:42:33 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 4, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 4, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:42:33 -06:00
Author
Owner
Copy Link

@mckaygerhard commented on GitHub (Feb 5, 2019):

this was resolved at 1.7.1 ?? what about 1.6.X ??? not all users have golang 1.11 and vendors provide security patches backported to golang 1.8 and 1.9!

@mckaygerhard commented on GitHub (Feb 5, 2019): this was resolved at 1.7.1 ?? what about 1.6.X ??? not all users have golang 1.11 and vendors provide security patches backported to golang 1.8 and 1.9!
GiteaMirror commented 2025-11-02 04:42:33 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Feb 5, 2019):

I do not believe anything for this has been implemented in any version.
You could edit the title to be a feature request or open another issue (probably the former) and wait for someone to pick it up and make a PR.

@jolheiser commented on GitHub (Feb 5, 2019): I do not believe anything for this has been implemented in any version. You could edit the title to be a feature request or open another issue (probably the former) and wait for someone to pick it up and make a PR.
GiteaMirror commented 2025-11-02 04:42:33 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Apr 6, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:42:34 -06:00
Author
Owner
Copy Link

@fnetX commented on GitHub (May 27, 2021):

This has been addressed? Seems to work by now.

@fnetX commented on GitHub (May 27, 2021): This has been addressed? Seems to work by now.
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 issue/confirmed type/enhancement
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#2624
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?