Repository navigation
Added feature RunAlways - #12
Merged
Merged
Conversation
Contributor
|
We have the same issue, we had been poking the files in our build pipeline to ensure the hash changed, but we would prefer this type of solution. |
Contributor
|
Thanks for the excellent PR. The unit tests and code were spot on. It is up on Nuget as version 1.4. |
Contributor
|
Please check out the docs page and let me know if you see any errors. https://github.com/ClearMeasure/AliaSQL/wiki/Getting-started |
|
👍 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Scripts in RunAlways folder will be executed always, not only when there are new/changed files like in Everytime folder.
It's a useful feature for scenarios when there are scripts that have to be run after every update (e.g. maintenance and integrity check scripts)