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

Git squash from Web interface #1544

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

Originally created by @ange007 on GitHub (Feb 18, 2018).

  • Gitea version (or commit ref): 283e87d
  • Git version: 2.15.0
  • Operating system: Debian 9
  • Database (use [x]):
    • SQLite

Description

Do you plan to implement a commits aggregation with Web interface?
Since now in the case of using the squash function in the history of the commits, all the previous commits still remain.

default

Or am I probably not doing something right? I use an example from here: https://stackoverflow.com/a/5201642

Originally created by @ange007 on GitHub (Feb 18, 2018). - Gitea version (or commit ref): 283e87d - Git version: 2.15.0 - Operating system: Debian 9 - Database (use `[x]`): - [x] SQLite ## Description Do you plan to implement a commits aggregation with Web interface? Since now in the case of using the **squash** function in the history of the commits, all the previous commits still remain. ![default](https://user-images.githubusercontent.com/2736539/36351299-352e465c-14b0-11e8-86c7-2c7c029bf54a.png) Or am I probably not doing something right? I use an example from here: https://stackoverflow.com/a/5201642
GiteaMirror added the issue/staleissue/needs-feedback labels 2025-11-02 04:04:29 -06:00
GiteaMirror commented 2025-11-02 04:04:30 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Feb 18, 2018):

Or commits remain in source branch or in target branch?

@lafriks commented on GitHub (Feb 18, 2018): Or commits remain in source branch or in target branch?
GiteaMirror commented 2025-11-02 04:04:30 -06:00
Author
Owner
Copy Link

@ange007 commented on GitHub (Feb 18, 2018):

I generate the union in the local repository and send the change to the remote repository.
In GitHub, this behavior worked fine (at least earlier).

@ange007 commented on GitHub (Feb 18, 2018): I generate the union in the local repository and send the change to the remote repository. In GitHub, this behavior worked fine (at least earlier).
GiteaMirror commented 2025-11-02 04:04:30 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Feb 18, 2018):

Can you create sample at try.gitea.io? In 1.4.0-rc1 there is already an option to squash merge pull request commits

@lafriks commented on GitHub (Feb 18, 2018): Can you create sample at try.gitea.io? In 1.4.0-rc1 there is already an option to squash merge pull request commits
GiteaMirror commented 2025-11-02 04:04:31 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 7, 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 7, 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.
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/needs-feedback issue/stale
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#1544
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?