-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve clarity in code and docs #1052
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: David Mertz <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! A couple minor changes added.
@@ -269,7 +269,7 @@ By default, the `docker_build.sh` script: | |||
- Uses the `PROJECT_NAME` specified in the `pyflyte init` command, which in | |||
this case is `my_project`. | |||
- Will not use any remote registry. | |||
- Uses the git sha to version your tasks and workflows. | |||
- Uses the git revision SHA1 to version your tasks and workflows. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Uses the git revision SHA1 to version your tasks and workflows. | |
- Uses the git revision ID (the SHA hash) to version your tasks and workflows. |
@@ -367,7 +367,7 @@ Let's break down what each flag is doing here: | |||
- `--archive`: This argument allows you to pass in a package file, which in | |||
this case is `flyte-package.tgz`. | |||
- `--version`: This is a version string that can be any string, but we recommend | |||
using the git sha in general, especially in production use cases. | |||
using the git revision in general, especially in production use cases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
using the git revision in general, especially in production use cases. | |
using the git revision ID (the SHA hash), especially in production use cases. |
Co-authored-by: Niels Bantilan <[email protected]> Signed-off-by: David Q Mertz <[email protected]>
looks like there are some linting issues. Will need to run pre-commit hooks to address those: https://docs.flyte.org/projects/cookbook/en/latest/contribute.html#pre-commit-hooks |
Only copy-edit style changes.
Attn: @ppiegaze