This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
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.
Description
The idea is to further improve the cache subscriptions mechanism, namely the one which allows us to save the last state of the monorepo and run tasks only over the changed files after it. It somewhat worked already, but one of the bugs was that if the output files of the task were removed, Garment would still think the project is consistent because the input files haven't been changed. I addressed it by creating a subscription for each output file, so if the output has been removed or manually changed, Garment would rerun the whole task. In the future we can also make it rerun the task only for the particular file responsible for that changed output.
During the work, I also noticed some major flaws in the mechanism and fixed them too.
Fixes # (issue)
How Has This Been Tested?
Only manually in the Garment repo itself
Checklist:
Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement