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
## Summary
Minor copy change to use the correct file name.
## How was it tested?
Manually read the content.
Signed-off-by: Mike Nikles <[email protected]>
Copy file name to clipboardExpand all lines: docs/app/docs/guides/pinning_packages.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ To add a specific version of a package with `<package_name>@<version>`. For exam
46
46
47
47
For packages that use semver, you can pin a range of versions for your project. For example, if you pin `python@3`, it will install the latest minor and patch version of `python >=3.0.0`. You can update to the newest package version that matches your criteria by running `devbox update`.
48
48
49
-
When you run a command that installs your packages (like `devbox shell` or `devbox install`), Devbox will generate a `Devbox.lock` file that contains the exact version and commit hash for your packages. You should check this file into source control to ensure that other developers will get the same environment.
49
+
When you run a command that installs your packages (like `devbox shell` or `devbox install`), Devbox will generate a `devbox.lock` file that contains the exact version and commit hash for your packages. You should check this file into source control to ensure that other developers will get the same environment.
0 commit comments