| Crates.io | reposcan |
| lib.rs | reposcan |
| version | 0.3.0 |
| created_at | 2025-02-02 16:53:17.709508+00 |
| updated_at | 2025-02-09 15:25:50.233648+00 |
| description | Command line tool for discovering local git repositories and keeping track of local and remote changes collectively. |
| homepage | |
| repository | https://github.com/chrfre/reposcan.git |
| max_upload_size | |
| id | 1539709 |
| size | 47,152 |
reposcan – a manager for git repositoriesCommand line tool for discovering local git repositories and keeping track of local and remote changes collectively.
Perhaps you find yourself using many git repositories to collaborate and keep track of versions in software development, scientific projects, or even your creative works. Then a tool such as this might be helpful by
There are currently no precompiled binaries available.
reposcan can be compiled from source via rust's cargo package manager from crates.io.
Instructions there can be found under the "Install".
If rust is not yet installed, visit rustup.rs for instructions.
A quick and crisp entry into using reposcan can be found by typing
reposcan --help
As a first step,
reposcan discover
will search the current directory and subdirectory for git repositories with a file tree. You will see
In a second step, you may either add the newly found repositories by typing
reposcan discover --add
or remove obsolete repositories by typing
reposcan discover --prune
Discovery and curation only consider the current working directory and its subdirectories, because these are potentially the most time-consuming operations. In contrast, checking the status and fetching are performed on all known repositories in the curated list independent of the current working directory.
Typing
reposcan status
lists changes to repositories that have changed files or are in an in-between state of merging, rebasing, etc.
Clean repositories will not show up.
By executing
reposcan fetch
all known repositories are entered and updated from all remotes.
Currently if an unauthenticated fetch fails (most likely due to required authentication), the fetching is repeated via a git subprocess.
If one has set up git to properly authenticate to a server, then authentication will also work with reposcan without the need to set it up seperately.
This solution is privacy-preserving insomuch that a user does not have to trust reposcan to handle their credentials.
reposcan list
will output all known repositories.
This project is not affiliated with the Git™ project nor with the Software Freedom Conservancy.