Reputation: 1681
I want to export the log of all commits in a repository to a text file. Is there a way to do this?
Upvotes: 129
Views: 151383
Reputation: 52716
You can make log report more clearly, by
(1) setting number of latest commits (for example, in below command, we get latest 50 commits, you can change it to 100, 500, etc.)
(2) display long commit in one line This command is display commit log in current branch:
git log --oneline -50 > log50_latest_commits.txt
(3) If you want display commit at all branch
git log --all --oneline -50 > log50_latest_commits.txt
Generated text file will stand at the current directory.
Reference: https://git-scm.com/docs/git-log
(tested on git version 2.11.0.windows.1
and it works on many other versions of Git)
Upvotes: 4
Reputation: 169
Use:
git log --pretty=format:"%h - %an, %ar : %s" > log.txt
This gives a clean and nice Git log.
Upvotes: 0
Reputation: 23845
This is what worked for me with Git Bash on Windows 7:
git log > /C/Users/<user-name>/Desktop/git-log.txt
Replace <user-name>
with your user name
.
The file will be exported to your desktop from where you can read it.
Upvotes: 2
Reputation: 807
In my case I found this was helpful
git log --after="2020-3-20" --pretty=format:'Author: %an %nDate/Time: %aD%nCommit: %s' | paste > log.txt
This will generate:
Author: your name
Date/Time: Commit Date time
Commit: Commit message
Upvotes: 3
Reputation: 2846
It’s been long since this question was asked and by that time things have been evolved.
But, it is very interesting that all answers here are correct but not really addressing a post command error which is also very common. Let’s try to understand...
Who knew it was super easy. Run a simple command
git log -p --all > git_log.txt
but then I struck on an error
> warning: inexact rename detection was skipped due to too many files.
> warning: you may want to set your diff.renameLimit variable to at least 2951 and retry the command.
And we had a problem. The output file was half a gigabyte.
We just wanted the first half of 2018 which we are able to do with --after
and --until
:
git log --pretty=format:"%ad - %an: %s" --after="2018-01-01" --until="2018-06-30" > git_log.txt
This worked nicely for our purposes and was nice to know that we could change the format if need be.
Upvotes: 10
Reputation: 97
It's simple. If you don't matter saving a file, you need to the open terminal
cd {your Git repository}
git log > your_file_name.txt
If you need a special directory, just write all paths on the right side, like this:
cd {your Git repository}
git log > /home/user/logs/your_file_name.txt
This directory, for example, you could use any one of your needs. I write a log like this just now.
This example show how to write a text in a file via Bash
Upvotes: 1
Reputation: 421
I found this article that could help you. Article of how generate a changelog. One tool that you could use is changelog
npm install generate-changelog -g
changelog generate
It will create a well-formed CHANGELOG.md file.
Upvotes: 1
Reputation: 717
git log | clip
copies to clipboard, then paste to a textfile.
(Especially if you have the problem of line-ending and thus by this method you can copy and paste it in a Microsoft word document(.docx); so there would be a new line for each commit!!!)
Upvotes: 28
Reputation: 617
git log --before="2019-2-23" --pretty=format:'"%h","%an","%ae","%aD","%s",' --shortstat --no-merges | paste - - - > log.txt
Upvotes: 13
Reputation: 408
You may use the >
symbol send the output to a file. For example:
git log > commits.txt
Upvotes: 12
Reputation: 53553
You'll just need to disable the pager.
git --no-pager log > log.txt
If you want to format it to look nicer, you can use parameters of git log.
Upvotes: 199