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

fix(build): make image tag lowecase #43

Merged
merged 1 commit into from
Dec 4, 2023
Merged

fix(build): make image tag lowecase #43

merged 1 commit into from
Dec 4, 2023

Conversation

0xE282B0
Copy link
Member

@0xE282B0 0xE282B0 commented Dec 3, 2023

No description provided.

@0xE282B0 0xE282B0 force-pushed the fix_push-action branch 2 times, most recently from c608ff3 to b24ad6e Compare December 3, 2023 20:28
@0xE282B0
Copy link
Member Author

0xE282B0 commented Dec 3, 2023

@flavio, do you know if there is a nicer way to lowercase the github.repository_owner than adding another step.

Copy link
Member

@flavio flavio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@0xE282B0 I didn't find any built-in function for that by looking at the documentation over there.

I'm fine with your proposal, but I made another one in the comments.

BTW, I'm sorry I didn't see that coming with my tests :(

@@ -53,6 +53,12 @@ jobs:
if: ${{ startsWith(github.ref, 'refs/tags/') }}
run: |
echo TAG_NAME=$(echo $GITHUB_REF | sed -e "s|refs/tags/||") >> $GITHUB_ENV
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about reusing this step and do something like:

Suggested change
echo TAG_NAME=$(echo $GITHUB_REF | sed -e "s|refs/tags/||") >> $GITHUB_ENV
echo TAG_NAME=$(echo $GITHUB_REF | sed -e "s|refs/tags/||") >> $GITHUB_ENV
echo REPOSITORY_NAME=$(echo {{ github.repository_owner }} | awk "{print tolower($0)}")) >> $GITHUB_ENV

I didn't try it on GH, but I think it should work and would just reduce the number of steps and keep things consistent

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It still feels odd that it takes so many changes to fix it.
But at least it is consistent and less steps.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW, I'm sorry I didn't see that coming with my tests :(

No worries, you tested everything else on your fork 😊.

@0xE282B0 0xE282B0 force-pushed the fix_push-action branch 2 times, most recently from aa36f90 to 438889f Compare December 4, 2023 20:59
@0xE282B0 0xE282B0 merged commit 2af7aef into main Dec 4, 2023
14 checks passed
@0xE282B0 0xE282B0 deleted the fix_push-action branch December 4, 2023 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants