-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add hooks #1218
Open
aawsome
wants to merge
13
commits into
main
Choose a base branch
from
hooks
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+445
−196
Open
feat: Add hooks #1218
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
b9e2263
fix: return exitcode
aawsome 9360397
feat: Add run-before and run-after hooks
aawsome e2ae782
dprint
aawsome 664361c
Use new type CommandInput
aawsome aa56f13
add more hooks
aawsome 36282a1
depend on rustic_core branch commandinput
aawsome 720307a
add docu, examples and tests
aawsome 261e9d1
Merge branch 'main'
aawsome 45c9159
adapt to rustic_core
aawsome 47b1950
update deps
aawsome d5f7cb4
Merge branch 'main'
aawsome 473ce7c
use hooks for targets in copy command
aawsome f311a17
remove no longer needed dep
aawsome File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we may want to release the changes first without re-introducing git dependencies again, changing them back later. Now that releasing should be just merging the release pr.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we wait for a release of rustic_core, we'll pile up PRs in rustic which depend on these things but cannot be merged. We won't have the features in the nightly builds and will not get any feedback until we release a rustic release.
As many changes in rustic are changes in rustic_core, I see no alternative than using a git dependency here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I understand. Do you think it would be viable to up the release cadence for
rustic_core
and say we do at least one release in a week with things that have been merged, even if small one's? It would be just a click away, we could release anotherrustic_core
version today, for example.