remove scenario-file (as a whole) from checks to re-run datapoints #232
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.
Resolves CLI issue 237
Pull Request Description
The change in this PR means changes to the scenario-file do not trigger re-running every datapoint (removes it from the 2nd list below).
Documenting out-of-date datapoints:
This check looks inside each datapoint specified in the scenario-file.
finished.job
file or anout.osw
file, it is re-runIf the most recent change to any out.osw file is older than the most recent change to any of the following project-dir files, the entire scenario is re-run.
in.osw
Gemfile
Gemfile.lock
mappers
folderChecklist (Delete lines that don't apply)