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
This resource tracks some useful metadata that is not written to files by the in command, which makes it impossible to reference that metadata during pipeline execution.
I think it would be fairly straightforward to update the in task to write the git_metadata to a file (or to write each entry in it to a separate file), but I'm not sure if:
it's not actually straightforward and/or
there are other reasons for not making these metadata available during pipeline execution
Assuming someone (e.g., me) is willing to implement the changes, are there known reasons not to include all of the metadata in the files produced by in?
The text was updated successfully, but these errors were encountered:
This resource tracks some useful metadata that is not written to files by the
in
command, which makes it impossible to reference that metadata during pipeline execution.I think it would be fairly straightforward to update the
in
task to write thegit_metadata
to a file (or to write each entry in it to a separate file), but I'm not sure if:Assuming someone (e.g., me) is willing to implement the changes, are there known reasons not to include all of the metadata in the files produced by
in
?The text was updated successfully, but these errors were encountered: