-
Notifications
You must be signed in to change notification settings - Fork 8
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
rename the cr file in the workflow #66
Conversation
- name: Rename CR file | ||
shell: bash | ||
env: | ||
CR_FILE: ${{ inputs.CR_FILE }} | ||
run: | | ||
# this is where all our default CRs are located. | ||
ln -s config/samples/default.yaml "./${CR_FILE}" |
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.
The name says Rename CR file
but the step actually creates a symbolic link!
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.
I thought "Create a symlink" might be harder to understand and the purpose of it might be even harder to understand. On the other hand, creating a symlink is a much cheaper operation compared to cp
or mv
but has a similar result.
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.
So, should I rename the step, or should I change the operation to cp
or mv
?
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.
IMO, rename it to Create Symlink for CR file
.
Also if the symlink already exists, this command will fail, otherwise you can use ln -sf
.
Description
Changes proposed in this pull request:
render-and-upload-manifests-reusable.yml
a logic to rename (really, create a symlink) the default CR was added, so that the CR can be uploaded with a different name (not possible via the gh cli).create-changelog
script and use it in thecreate-draft-release
workflow instead of using a script located at the repo.get-version-from-branch.sh
because it is no longer needed since the introduction ofget-version-from-release-branch-reusable.yml
. It was not used in any place so for, so it's safe to remove it.Related issue(s)