Pinning the Code Revision That Produced a Result
The outcome names code as one of the three things a result must be re-derivable from. Cloud runs make this sharper, not looser: the code is shipped to a machine you will never see again, so if the revision was not captured at submit time it is gone. The node is about the provenance obligation, not about learning a version-control tool.
This Concept is waiting for its first lesson!
The outcome names code as one of the three things a result must be re-derivable from. Cloud runs make this sharper, not looser: the code is shipped to a machine you will never see again, so if the revision was not captured at submit time it is gone. The node is about the provenance obligation, not about learning a version-control tool.
Are you a teacher? Sign in to start contributing.
Sign In