github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 11:56:41 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[Proposal]: ability to generate ports to other branches #4677

New Issue
Closed
opened 2025-11-02 05:59:09 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 05:59:09 -06:00
Owner
Copy Link

Originally created by @guillep2k on GitHub (Jan 17, 2020).

It would be cool for a merged PR that there would be a [Generate port] button to create a backport/frontport of the merged commit on another branch.

Originally created by @guillep2k on GitHub (Jan 17, 2020). It would be cool for a merged PR that there would be a `[Generate port]` button to create a backport/frontport of the merged commit on another branch.
GiteaMirror added the type/featuretype/proposal labels 2025-11-02 05:59:09 -06:00
GiteaMirror commented 2025-11-02 05:59:10 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Jan 17, 2020):

In addition, the PR would have some visual cue that the port is faithful.

This would only work for ports that generate no conflicts, and of course they need to pass the revision process because ports may cause problems even if they merge cleanly.

@guillep2k commented on GitHub (Jan 17, 2020): In addition, the PR would have some visual cue that the port is faithful. This would only work for ports that generate no conflicts, and of course they need to pass the revision process because ports may cause problems even if they merge cleanly.
GiteaMirror commented 2025-11-02 05:59:10 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jan 17, 2020):

I'm actually thinking it would be good for us to have a way of importing a patch to or as a branch.

If we have that, then lots of things can hang off that base code.

@zeripath commented on GitHub (Jan 17, 2020): I'm actually thinking it would be good for us to have a way of importing a patch to or as a branch. If we have that, then lots of things can hang off that base code.
GiteaMirror commented 2025-11-02 05:59:10 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Jan 18, 2020):

git apply patchfile

@6543 commented on GitHub (Jan 18, 2020): `git apply` **patchfile**
GiteaMirror commented 2025-11-02 05:59:12 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Jan 18, 2020):

@zeripath but before this #9014 should be implemented ...

@6543 commented on GitHub (Jan 18, 2020): @zeripath but before this #9014 should be implemented ...
GiteaMirror commented 2025-11-02 05:59:12 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 18, 2020):

I think it's a duplicate of #3880

@lunny commented on GitHub (Jan 18, 2020): I think it's a duplicate of #3880
GiteaMirror commented 2025-11-02 05:59:13 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Jan 18, 2020):

I think it's a duplicate of #3880

You're right. Closing this.

@guillep2k commented on GitHub (Jan 18, 2020): > > > I think it's a duplicate of #3880 You're right. Closing this.
GiteaMirror commented 2025-11-02 05:59:13 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jan 19, 2020):

@6543 I suspect they might need each other

@zeripath commented on GitHub (Jan 19, 2020): @6543 I suspect they might need each other
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/feature 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#4677
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?