Releases: AkashRajpurohit/git-sync
v0.11.2
Changelog
- 58acbe4 chore(deps): update golang docker tag to v1.23.3 (#64)
- 3c48bfb chore(deps): update module codeberg.org/mvdkleijn/forgejo-sdk/forgejo to v1.2.0 (#61)
- f822b4b chore(deps): update module github.com/ktrysmt/go-bitbucket to v0.9.81 (#60)
- 2a6ef08 chore(deps): update module github.com/xanzy/go-gitlab to v0.112.0 (#59)
- bc4367b chore(deps): update module github.com/xanzy/go-gitlab to v0.113.0 (#62)
- b999328 chore(deps): update module golang.org/x/oauth2 to v0.24.0 (#65)
- 795d358 chore(deps): 🚀 upgrade go.mod to Go 1.23.3
- ee14352 chore: ♻️ go mod tidy
- 4ab9a83 chore: 🚚 code refactor for util functions
- 294686f ci: 🚚 move to stale action since stale bot is deprecated.
- 8507e0f ci: 🔧 add permissions
- e5b4135 ci: 🔧 add stale.yml
- d880b67 ci: 🔧 add workflow dispatch
- d658f6b feat: ✅ utils function tests added
- 8ba23cc fix(pkg/sync): 🔧 log error details without crashing
v0.11.1
Changelog
- 4c0389e build(deps): ⬆️ upgrade go to 1.23.2
- eb96022 chore(deps): update golang docker tag to v1.23.2 (#51)
- 082c787 chore(deps): update module github.com/google/go-github/v65 to v66 (#56)
- 3117d47 chore(deps): update module github.com/google/go-github/v65 to v66 (#57)
- f01c575 chore(deps): update module github.com/xanzy/go-gitlab to v0.111.0 (#54)
- 88b1bb8 chore: ♻️ remove labels
- 20b04da chore: 🚚 move initial config fetcher to config package
- 38d164f chore: 🔧 update step name
- db66fc7 ci: 🩹 pass build args correctly
- 8413ce3 ci: 🔧 run tests on CI
- 7302046 ci: 🔧 update multi-platform build to run on different runners
- bbf6b40 feat: ✨ use cache between docker builds
- 4741a1f feat: ✅ validate config test added
- 588fab8 fix: 🐛 pass build args as list instead of csv
- 9fd19cd fix: 🐛 sync using origin remote by default (#55)
v0.11.0
What's New ❕
git-sync
now supports a new config option called clone_type
. By default git-sync
performs a bare clone of your repository code.
However with this new release, you can now specify which type of clone you want to perform.
The available options are bare
, shallow
, mirror
or full
. The default value is bare
(to maintain backward compatibility).
Update your config file as mentioned in the docs to use this new feature.
Changelog
- 9a3e9fe feat: ✨ allow different clone type options
v0.10.1
v0.10.0
What's New ❕
git-sync
now adds support for another client, which is forgejo
.
Thanks to @jbonadiman for adding the support! 🎉
Changelog
- 81b295e feat: ✨ forgejo support added
v0.9.1
v0.9.0
What's New ❕
This release is specifically for docker users, you can now pass PGID
and PUID
environment variables while running git-sync. This will help in ensuring there are no file/folder permission issues for the backups that are created. You can control which user will own your backup files on the host OS.
It is advised to pass these variables, you can read more about this in the docker installation guide
Changelog
- 5d05110 build(deps): ⬆️ go-github upgraded to v64
- 0009685 build: 🐳 additional labels added to docker container
- 41fdc77 build: 🔧 add short commit to snapshot version template
- 08836ea build: 🔧 go version updated to 1.23.0
- e9d767f chore(deps): update golang docker tag to v1.23.0
- 5bfbed0 chore(deps): update module github.com/google/go-github/v63 to v64
- 493c4f4 chore(deps): update module github.com/robfig/cron/v3 to v3.0.1
- df2d2e5 chore: 🔧 update Dockerfile to set permissions for the working directory and switch to a new user
- 2bff36c chore: 🔧 update goreleaser config to use project name in checksum and version templates
- 554e513 feat: ✨ allow user to pass PGID and PUID for docker to create the directories as per the specified user and group
v0.8.2
v0.8.1
v0.8.0
What's New
With this release, now git-sync allows users to be able to synchronize not just code repositories but also Wiki's! 🎉
To include wiki's in your backup process, add the include_wiki
to true
in your config file.
⚠️ Breaking Change
While the addition of new config key include_wiki
is optional, the breaking change is about the folder structure on your local system where the backups are created. The new structure will be like this:
- Repo: backup_dir -> RepoOwner -> RepoName -> RepoName.git
- Wiki: backup_dir -> RepoOwner -> RepoName -> RepoName.wiki.git
To ensure you have a smooth transition, it is advised that you can just choose a different backup_dir
and start fresh or if you already have access to your backed up codebases then feel free to delete those and start fresh. In the first run, git-sync
will start with cloning process as per the new directory structure.