Skip to content
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

Merged
merged 8 commits into from
Feb 2, 2024

Conversation

friedrichwilken
Copy link
Contributor

@friedrichwilken friedrichwilken commented Feb 1, 2024

Description

Changes proposed in this pull request:

  • In the workflow 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).
  • Add the create-changelog script and use it in the create-draft-release workflow instead of using a script located at the repo.
  • remove get-version-from-branch.sh because it is no longer needed since the introduction of get-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)

@friedrichwilken friedrichwilken requested a review from a team as a code owner February 1, 2024 20:24
@kyma-bot kyma-bot added area/ci Issues or PRs related to CI related topics cla: yes Indicates the PR's author has signed the CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 1, 2024
@kyma-bot kyma-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 2, 2024
@kyma-bot kyma-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 2, 2024
Comment on lines 38 to 44
- 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}"
Copy link
Contributor

@marcobebway marcobebway Feb 2, 2024

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!

Copy link
Contributor Author

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.

Copy link
Contributor Author

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?

Copy link
Contributor

@marcobebway marcobebway Feb 2, 2024

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.

@kyma-bot kyma-bot added the lgtm Looks good to me! label Feb 2, 2024
@kyma-bot kyma-bot merged commit b3ca34f into kyma-project:main Feb 2, 2024
5 checks passed
@friedrichwilken friedrichwilken deleted the fix-renaming branch February 2, 2024 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci Issues or PRs related to CI related topics cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants