Describe the bug
The custom flavor builder CLI generates workflows which call the custom flavor builder action with CUSTOM_FLAVOR_BUILD_REPO: ${{ github.repository }}. When this is used from a repo which contains capital letters in the owner (organization or user) or repository name, it results in a job failure because Docker does not allow uppercase characters in image names.
When setting the environment variable value to use all lowercase (statically or dynamically), the build succeeds, but the job still fails because the Tag and Push Docker Image step still uses ${{ github.repository }} directly as opposed to using the input.
To Reproduce
Steps to reproduce the behavior:
- Create a repository with uppercase characters in the repo name
- Call the action with
CUSTOM_FLAVOR_BUILD_REPO: ${{ github.repository }}
- Run the build and encounter the first issue described above.
- Set the value statically to all lowecase.
- Run the build and encounter the second issue described above
Expected behavior
The input should be converted to lowercase and used consistently to avoid this problem
Screenshots
N/A
Additional context
N/A
Describe the bug
The custom flavor builder CLI generates workflows which call the custom flavor builder action with
CUSTOM_FLAVOR_BUILD_REPO: ${{ github.repository }}. When this is used from a repo which contains capital letters in the owner (organization or user) or repository name, it results in a job failure because Docker does not allow uppercase characters in image names.When setting the environment variable value to use all lowercase (statically or dynamically), the build succeeds, but the job still fails because the
Tag and Push Docker Imagestep still uses${{ github.repository }}directly as opposed to using the input.To Reproduce
Steps to reproduce the behavior:
CUSTOM_FLAVOR_BUILD_REPO: ${{ github.repository }}Expected behavior
The input should be converted to lowercase and used consistently to avoid this problem
Screenshots
N/A
Additional context
N/A