Skip to content

Commit 6359aed

Browse files
authored
Fix broken link
1 parent 5fb3d2f commit 6359aed

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/src/project.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ datadir() * "/foo/test.bson" # not recommended
9999

100100
## Reproducibility
101101
The project setup approach that DrWatson suggests is designed to work flawlessly with Julia standards, to be easy to share and to be fully reproducible. There are three reasons that **true** reproducibility is possible:
102-
1. The project's used packages are embedded in the project because of `Manifest.toml`
102+
1. The project's used packages are embedded in the project because of `Manifest.toml`.
103103
2. The navigation around the folders of the project uses local directories.
104104
3. The project is a Git repository, which means that it has a detailed (and re-traceable) history of all changes and additions.
105105

@@ -112,5 +112,5 @@ pkg> instantiate
112112
to use your project (*assuming of course that you are both using the same Julia installation and version*).
113113
All required packages and dependencies will be installed and then any script that was running in your computer will also be running in their computer **in the same way!**
114114

115-
In addition, with DrWatson you have the possibility of "tagging" each simulation created with the commit id, see the discussion around [`current_commit`](@ref) and [`tag!`](@ref).
115+
In addition, with DrWatson you have the possibility of "tagging" each simulation created with the commit id, see the discussion around [`gitdescribe`](@ref) and [`tag!`](@ref).
116116
This way, any data result obtained at any moment can be truly reproduced simply by resetting the Git tree to the appropriate commit and running the code.

0 commit comments

Comments
 (0)