How to create reflogs information in an existing bare repository

As you might have known that by default, git doesn’t enable reflog updates for new bare repositories. The problem is, I have a long history repository but it was created before I set the flag “logAllRefUpdates” on, and now I want that information for another application to work.

How can I achieve that with minimal changes made to the existing repository. A very simple solution is pushing a new commit which I don’t want to (!) 🙂

  • Working with abandoned pull requests on Github (keeping history)
  • Git list : viewing git repositories in home folder
  • Does deleting a branch in git remove it from the history?
  • Update files from an exported Git repository offline
  • Unable to clone repository with a Bambo Remote Agent
  • Trying to create git repository and commit files to it but with no luck
  • Push local Git branch to origin
  • Git ignore this kind of files?
  • Broken references in a cloned git repo
  • GitHub: Permission denied (publickey). fatal: The remote end hung up unexpectedly
  • How to prevent author of Git commit from being changed
  • How can i configure imported repository path in GitLab to remove root folder prefix?
  • One Solution collect form web for “How to create reflogs information in an existing bare repository”

    The reflog is a relatively simple file format. Here’s an example:

    ] cat .git/logs/HEAD|sed 's/\t/<TAB>/'
    0000000000000000000000000000000000000000 5cfe4256d98af22a570c78c5e3048391a90f5f98 Joe User <> 1306427954 -0400<TAB>clone: from git://

    You can manually construct appropriate reflogs by following the same format:

    previous-ref-or-zero new-ref User Name <user@email> unix-timestamp timezone\tmessage

    Just create one of these for each ref. You can probably do this directly with git for-each-ref with an appropriate format string (thanks, Chris!)

    Git Baby is a git and github fan, let's start git clone.