Skip to content

Force pushing after first commit #3756

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
realies opened this issue Apr 3, 2018 · 5 comments
Closed

Force pushing after first commit #3756

realies opened this issue Apr 3, 2018 · 5 comments
Labels
issue/stale type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@realies
Copy link

realies commented 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.

@lafriks
Copy link
Member

lafriks commented Apr 4, 2018

What version are you using?

@lafriks lafriks added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Apr 4, 2018
@realies
Copy link
Author

realies commented Apr 4, 2018

4c6e170

@diocloid
Copy link

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.

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Jan 28, 2019
@stale
Copy link

stale bot commented Feb 18, 2019

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

@stale stale bot closed this as completed Feb 18, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/stale type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

3 participants