-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[wishlist] Server-side reflog #14865
Comments
why not just set this value in the gitea user's .gitconfig? |
Why not just user bare repositories, command line git and regular SSH access instead of this Gitea thing? :-) Of course you can set this value per repository, as long as you are the server administrator. It would be nice to let repository owners set this with Gitea web interface; also possibly make it default per server, per user, per organization etc. |
This PR adds support for reflogs on all repositories. It does this by adding a global configuration entry. Implements #14865 --------- Signed-off-by: Philip Peterson <philip.c.peterson@gmail.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
This PR adds support for reflogs on all repositories. It does this by adding a global configuration entry. Implements go-gitea#14865 --------- Signed-off-by: Philip Peterson <philip.c.peterson@gmail.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Backport #22451 by @philip-peterson This PR adds support for reflogs on all repositories. It does this by adding a global configuration entry. Implements #14865 Signed-off-by: Philip Peterson <philip.c.peterson@gmail.com> Co-authored-by: Philip Peterson <philip-peterson@users.noreply.github.com>
This has been implemented now via config option. Issue can likely be closed. |
There should be an option to enable server-side reflog for all or specific repositories. This is very helpful when somebody accidentally
push -f
https://stackoverflow.com/questions/48769443/git-reflog-in-bare-repository-with-core-logallrefupdates-set-true-returns-nothin
The text was updated successfully, but these errors were encountered: