Force pushing after first commit #1675

New Issue

GiteaMirror · 2025-11-02T04:09:12-06:00

GiteaMirror commented

2025-11-02 04:09:12 -06:00

Originally created by @realies on GitHub (Apr 3, 2018).

When creating a repo and having an initial commit, then forcing pushing the second commit, the preview of the changed file in Gitea shows there is only one commit. Going to the repository home, it says there's two commits. When previewing the changed file on the master branch, it looks like it's a mix between the initial commit and the force pushed change.

Originally created by @realies on GitHub (Apr 3, 2018). When creating a repo and having an initial commit, then forcing pushing the second commit, the preview of the changed file in Gitea shows there is only one commit. Going to the repository home, it says there's two commits. When previewing the changed file on the master branch, it looks like it's a mix between the initial commit and the force pushed change.

GiteaMirror added the type/question issue/stale labels 2025-11-02 04:09:12 -06:00

GiteaMirror closed this issue

2025-11-02 04:09:13 -06:00

GiteaMirror commented

2025-11-02 04:09:13 -06:00

@lafriks commented on GitHub (Apr 4, 2018):

What version are you using?

@lafriks commented on GitHub (Apr 4, 2018): What version are you using?

GiteaMirror commented

2025-11-02 04:09:13 -06:00

@realies commented on GitHub (Apr 4, 2018):

4c6e170

@realies commented on GitHub (Apr 4, 2018): `4c6e170`

GiteaMirror commented

2025-11-02 04:09:14 -06:00

@diocloid commented on GitHub (Apr 16, 2018):

This may be the same Issue as described here: #2898

I had the same Issue on multiple different Systems (x86 & ARM) with Debian Jessie.
After upgrading to Debian Stretch it works.

@diocloid commented on GitHub (Apr 16, 2018): This may be the same Issue as described here: #2898 I had the same Issue on multiple different Systems (x86 & ARM) with Debian Jessie. After upgrading to Debian Stretch it works.

GiteaMirror commented

2025-11-02 04:09:14 -06:00

@stale[bot] commented on GitHub (Jan 28, 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 (Jan 28, 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:09:14 -06:00

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

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 18, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 11:59:40 -06:00

[PR #1675] [MERGED] Fix static files permission under public/ #15988

Sign in to join this conversation.