This is an automated email from the ASF dual-hosted git repository. ephraimanierobi pushed a commit to branch v2-5-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit d2840e97cf0e2839856329152369f8368b628a1d Author: Jarek Potiuk <[email protected]> AuthorDate: Sun Jan 29 14:18:35 2023 +0100 Fix commit message for constraints (#29215) A long time ago in a galaxy far away ... We had a code that make our CI variables independent from the CI Actions used and we used CI_* prefixes to distinguish those values. This reflected the time when we moved from Travis to GitHub Actions and we wanted to keep the possibility to support both. Those variables have been since removed, but there was that one single planet (err. script) where the remnant of the old Jedi order (err. variables) remained and they caused rather meaningless commit messages for constraints. This PR updates the commit messages to be more meaningful, including direct links to the action that updated the constraints and helpful description on how you can easily run breeze with the exact set of dependencies that were used for it. (cherry picked from commit c7aa0bf91ce2624db3f3075d7e2a3bf4927dca15) --- scripts/ci/constraints/ci_commit_constraints.sh | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/scripts/ci/constraints/ci_commit_constraints.sh b/scripts/ci/constraints/ci_commit_constraints.sh index 3d4485db58..1170b0fdcf 100755 --- a/scripts/ci/constraints/ci_commit_constraints.sh +++ b/scripts/ci/constraints/ci_commit_constraints.sh @@ -23,8 +23,12 @@ git diff --color --exit-code --ignore-matching-lines="^#.*" || \ git commit --all --message "Updating constraints. Github run id:${GITHUB_RUN_ID} This update in constraints is automatically committed by the CI 'constraints-push' step based on -HEAD of '${CI_REF}' in '${CI_TARGET_REPO}' -with commit sha ${COMMIT_SHA}. +'${GITHUB_REF}' in the '${GITHUB_REPOSITORY}' repository with commit sha ${GITHUB_SHA}. + +The action that build those constraints can be found at https://github.com/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID}/ + +The image tag used for that build was: ${IMAGE_TAG}. You can enter Breeze environment +with this image by running 'breeze shell --image-tag ${IMAGE_TAG}' All tests passed in this build so we determined we can push the updated constraints.
