mirrors
/
goop
mirror of https://github.com/nyancrimew/goop.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Mirror of nyancrimew/goop@github.com
30 Commits 2 Branches 0 Tags 184 KiB
Go 100%
Go to file
maia tillie arson crimew 08d74d8c9b performance and edge case handling improvements 
+ new, better and cuter logging
 		2021-10-20 20:57:29 +02:00
cmd performance and edge case handling improvements 2021-10-20 20:57:29 +02:00
internal performance and edge case handling improvements 2021-10-20 20:57:29 +02:00
pkg/goop performance and edge case handling improvements 2021-10-20 20:57:29 +02:00
.gitignore Basic implementation to support sites with AutoIndex on 2020-10-30 11:47:23 +01:00
LICENSE Add readme and license 2020-10-30 18:48:44 +01:00
README.md Update README 2020-11-12 20:49:10 +01:00
go.mod performance and edge case handling improvements 2021-10-20 20:57:29 +02:00
go.sum performance and edge case handling improvements 2021-10-20 20:57:29 +02:00
main.go performance and edge case handling improvements 2021-10-20 20:57:29 +02:00

README.md

goop

Yet another tool to dump a git repository from a website. Code structure and console outputs heavily inspired by arthaud/git-dumper.

Usage

usage: goop [flags] url [dir]

Flags:
   -f, --force   overrides DIR if it already exists
   -h, --help    help for goop

Example

$ goop example.com

Installation

GO111MODULE=on go get -u github.com/deletescape/goop

How does it work?

The tool will first check if directory listing is available. If it is, then it will just recursively download the .git directory (what you would do with wget).

If directory listing is not available, it will use several methods to find as many files as possible. Step by step, git-dumper will:

  • Fetch all common files (.gitignore, .git/HEAD, .git/index, etc.);
  • Find as many refs as possible (such as refs/heads/master, refs/remotes/origin/HEAD, etc.) by analyzing .git/HEAD, .git/logs/HEAD, .git/config, .git/packed-refs and so on;
  • Find as many objects (sha1) as possible by analyzing .git/packed-refs, .git/index, .git/refs/* and .git/logs/*;
  • Fetch all objects recursively, analyzing each commits to find their parents;
  • Run git checkout . to recover the current working tree