Closed MSevey closed 1 month ago
.github/workflows/ci-release.yml (3)
`11-11`: **Tag pattern updated to use wildcard** The tag pattern has been updated to use a more general wildcard regex `"v*"`. This change is in line with the PR objective and should prevent issues with building images for specific tags like 'arabica'. Let's verify if this change affects any other parts of the workflow: ```shell #!/bin/bash # Description: Check if the new tag pattern is used consistently across the workflow # Test: Search for other tag patterns in the file rg --type yaml 'tags:' .github/workflows/ci-release.yml -A 5 ``` --- Line range hint `1-30`: **Docker workflow update not found in this file** The PR objectives mention updating the Docker workflow with necessary input parameters for manual triggering. However, these changes are not present in this file. Let's check if there are any Docker-related workflows in the repository: ```shell #!/bin/bash # Description: Search for Docker-related workflow files # Test: Look for workflow files that might contain Docker-related content fd -e yml -e yaml . .github/workflows | xargs rg --type yaml -l 'docker|image|container' ``` If the Docker workflow update is missing, would you like me to help create a new workflow file or update an existing one to include the necessary input parameters for manual triggering? --- `9-9`: **Branch pattern updated to use wildcard** The branch pattern has been updated to use a more general wildcard regex `"v*"`. This change aligns with the PR objective of implementing a more flexible pattern for future developments. Let's verify if this change affects any other parts of the workflow:.github/workflows/docker-build-publish.yml (3)
`8-8`: **Simplified branch pattern improves flexibility** The change from specific version patterns to the more general "v*" pattern is a good improvement. This simplification aligns with the PR objective of implementing a more general wildcard regex. It will match all version branches while reducing maintenance overhead for updating specific version patterns in the future. --- `10-10`: **Generalized tag pattern addresses PR objective** The change to a more general "v*" pattern for tags is an excellent improvement. This simplification not only makes the workflow more flexible but also directly addresses the PR objective of preventing issues with building images when specific tags (like 'arabica') are added. The new pattern will match all version tags while allowing for additional naming conventions in the future. --- `27-27`: **Added flexibility with `checkout_ref` parameter** The addition of the `checkout_ref` parameter to both `docker-security-build` and `docker-txsim-build` jobs is a valuable improvement. This change directly addresses the PR objective of introducing necessary input parameters for manual workflow triggers. It allows for greater flexibility in the CI process by enabling builds from specific branches, tags, or commits when manually triggered. To ensure this change is implemented correctly, let's verify the workflow structure: Also applies to: 38-38
Overview
This PR adds the required input for the using the docker workflow when manually triggered.
This PR also updates the regex matching to a more general wildcard regex for more flexibility in the future to avoid issues like images not being built due to adding
arabica
to the tag.