You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could see uncommitted diff from myproject/build-workflow listed in the log files. This is the case for git vc, haven't tested svn.
The rose-stem pattern often sees test workflows embedded in much larger projects, listing the diff of the whole project would be over the top for Cylc purposes. It could be useful for provenance, however, Cylc doesn't capture full information about its run environment so should this be captured via other means?
Question:
Should we restrict this to just show changes from within the workflow source directory? - Yes
Pull requests welcome!
The text was updated successfully, but these errors were encountered:
Should we restrict this to just show changes from within the workflow source directory?
IMO yes. That's all that affects the running of the workflow in question (unless it accesses external files, which could just as well be anywhere, not just under an umbrella project source),
The
log/version/
files log changes for files that aren't in the workflow source dir.For example if we have this directory structure:
And we install like so:
$ cylc install -c 'myproject/test-workflow'
We could see uncommitted diff from
myproject/build-workflow
listed in the log files. This is the case forgit
vc, haven't testedsvn
.The
rose-stem
pattern often sees test workflows embedded in much larger projects, listing the diff of the whole project would be over the top for Cylc purposes. It could be useful for provenance, however, Cylc doesn't capture full information about its run environment so should this be captured via other means?Question:
Pull requests welcome!
The text was updated successfully, but these errors were encountered: