-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
edea358
commit f4339f1
Showing
12 changed files
with
819 additions
and
665 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
# Maintenance | ||
|
||
## Upgrading the restic version | ||
|
||
1. Use `./scripts/update-restic.sh` to update the submodule. It automatically pushes a modified tag to the custom restic fork on Github. | ||
2. Update the README. | ||
3. Use `go mod tidy` to fetch all the modules and remove the unused ones. | ||
4. Use `./scripts/update-cmd.sh` to update the repository opening code. | ||
- If the patch fails, use `diff -u restic/cmd/restic/global.go cmd/git-remote-restic/restic.go > scripts/update-cmd.patch` to update it. | ||
5. Use `make test` to verify everything still works. | ||
- Use `git log -pG <pattern>` to identify commits that changed APIs that are now broken. | ||
6. Make a commit. | ||
7. Use `make release` to compile a new release. | ||
8. Push everything to Github, and make a new release there. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.