Wire up repo pushes

This commit is contained in:
2026-07-07 01:07:34 -04:00
parent bc771c1b4d
commit 3f1bc4d02f
4 changed files with 171 additions and 36 deletions
+5 -5
View File
@@ -1,9 +1,9 @@
# go-gitea-vendor
Want to vendor all your Go projects on your personal Gitea instance?
Don't want to bloat your git history?
Use `go-gitea-vendor` to maintain a separate repo that is only the latest vendoring!
Want to vendor all your public Go projects hosted on your personal Gitea instance?
Don't want to bloat your git history and exhaust your storage?
Use `go-gitea-vendor` to maintain separate, shallow-clone repos that hold only the latest commit and vendored dependencies for each of your Go projects!
## Usage
`echo 'EXAMPLE_API_TOKEN' | go-gitea-vendor https://gitea.example.com`
`echo 'EXAMPLE_API_TOKEN' | go-gitea-vendor https://gitea.example.com <username> [output organization]`
I recommend setting up a chron job or some form of automation for this.
I recommend setting up a chron job or some form of automation for this. My deployment involves running this on my Gitea mirror (this server mirrors my main Gitea instance as well as my GitHub) weekly using a chron job, then my main Gitea instance mirrors the output repos from this tool.