adding push condition - change to pyproject toml file; adding event i…

[radkalyan]

…nput vars to env vars

Description

Adding push condition change to python builder - change to pyproject toml file

Changes Made

• Adding push condition change - any change to pyproject toml will trigger python builder
• Fixing the environment variables - passing in workflow dispatch variables dynamically

How to Test

1. Check in changes to dev branch - this should trigger the build
2. Or, can trigger the workflow manually

Notes

[github-actions]

@CodiumAI-Agent /describe

[github-actions]

@CodiumAI-Agent /review

[github-actions]

@CodiumAI-Agent /improve

[QodoAI-Agent]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Incorrect context syntax The workflow references github.events.input which is incorrect; the proper context is github.event.inputs. This typo can cause syntax errors and undefined values. PYTHON_VERSION: ${{ github.events.input.python_version }} COMPUTE_TYPE: ${{ github.events.input.compute_type }} BASE_REGISTRY: ${{ github.events.input.base_registry }} BASE_IMAGE: ${{ github.events.input.base_image }} BASE_TAG: ${{ github.events.input.base_tag }} Undefined env on push Environment variables sourced from workflow_dispatch inputs will be undefined when the workflow is triggered by a push event. Consider providing defaults or conditionally setting these variables. PYTHON_VERSION: ${{ github.events.input.python_version }} COMPUTE_TYPE: ${{ github.events.input.compute_type }} BASE_REGISTRY: ${{ github.events.input.base_registry }} BASE_IMAGE: ${{ github.events.input.base_image }} BASE_TAG: ${{ github.events.input.base_tag }}

[QodoAI-Agent]

PR Code Suggestions ✨

Category	Suggestion	Impact
Possible issue	Correct input context reference Use the correct context for workflow_dispatch inputs: the github.event.inputs attribute (plural inputs on github.event) instead of github.events.input. .github/workflows/python-builder.yml [49-53] -PYTHON_VERSION: ${{ github.events.input.python_version }} -COMPUTE_TYPE: ${{ github.events.input.compute_type }} -BASE_REGISTRY: ${{ github.events.input.base_registry }} -BASE_IMAGE: ${{ github.events.input.base_image }} -BASE_TAG: ${{ github.events.input.base_tag }} +PYTHON_VERSION: ${{ github.event.inputs.python_version }} +COMPUTE_TYPE: ${{ github.event.inputs.compute_type }} +BASE_REGISTRY: ${{ github.event.inputs.base_registry }} +BASE_IMAGE: ${{ github.event.inputs.base_image }} +BASE_TAG: ${{ github.event.inputs.base_tag }} Suggestion importance[1-10]: 9 __ Why: The suggestion fixes the incorrect GitHub Actions context github.events.input to the correct github.event.inputs, which would otherwise prevent the workflow from picking up the inputs.	High
General	Separate push conditions Split the push trigger into two entries to OR‐combine branch updates and path changes, since branches+paths are AND‐filtered by default. .github/workflows/python-builder.yml [31-36] -push: - branches: [ "dev", "main"] - paths: - - 'docker/Dockerfile.python' - - 'py/install_config/pyproject.toml' - - '.github/workflows/python-builder.yml' +on: + push: + - branches: [ "dev", "main"] + paths: + - 'docker/Dockerfile.python' + - '.github/workflows/python-builder.yml' + - paths: + - 'py/install_config/pyproject.toml' Suggestion importance[1-10]: 6 __ Why: Splitting the push trigger into multiple mappings correctly implements OR semantics between branches and paths, improving trigger flexibility and aligning with GitHub Actions behavior.	Low

[github-actions]

@CodiumAI-Agent /update_changelog

[QodoAI-Agent]

Changelog updates: 🔄

2025-05-07 #790

Changed

• Trigger python-builder workflow on pyproject.toml changes
• Pass environment variables from workflow dispatch inputs

to commit the new content to the CHANGELOG.md file, please type:
'/update_changelog --pr_update_changelog.push_changelog_changes=true'