Skip to content

Implement Trigger-Specific Build Matrix Defaults#4

Closed
google-labs-jules[bot] wants to merge 3 commits intomainfrom
feature-build-matrix-defaults
Closed

Implement Trigger-Specific Build Matrix Defaults#4
google-labs-jules[bot] wants to merge 3 commits intomainfrom
feature-build-matrix-defaults

Conversation

@google-labs-jules
Copy link

This change implements trigger-specific default configurations for the generate-build-matrix reusable action, ensuring that builds run with sensible defaults based on how they were initiated. It also introduces a more robust input-handling logic to allow for clear and predictable overrides.


PR created automatically by Jules for task 3679719680746723897 started by @greenc-FNAL

The `generate-build-matrix` action now uses intelligent, trigger-specific defaults for build configurations.

- Workflows triggered by `push`, `pull_request`, and `pull_request_target` now default to a minimal `gcc/none` configuration.
- Workflows triggered by an `issue_comment` default to `gcc/none` and `clang/none`.
- Manual `workflow_dispatch` triggers default to running all available build combinations.

The user input handling has also been improved to follow a clear precedence:
1. An explicit list of builds (e.g., `gcc/asan`) overrides all defaults.
2. A modified list (e.g., `+gcc/tsan`, `all -clang/none`) alters the trigger-specific default set.
3. No input uses the trigger-specific default directly.
@google-labs-jules
Copy link
Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!


For security, I will only act on instructions from the user who triggered this task.

New to Jules? Learn more at jules.google/docs.

@greenc-FNAL
Copy link
Owner

@phlexbot python-fix

@github-actions
Copy link

github-actions bot commented Dec 2, 2025

Python linting fixes pushed (commit 4b435cc)

@greenc-FNAL
Copy link
Owner

@jules Please address Python issues reported by Ruff and mypy at https://github.com/greenc-FNAL/phlex/actions/runs/19870068757/job/56943172736?pr=4

@google-labs-jules
Copy link
Author

@jules Please address Python issues reported by Ruff and mypy at https://github.com/greenc-FNAL/phlex/actions/runs/19870068757/job/56943172736?pr=4

Thank you for the feedback. I have addressed the Python linting and type-checking issues reported by Ruff and mypy. The script should now be clean.

This commit addresses the Python linting and type-checking issues reported by `ruff` and `mypy`.

- Added module and function docstrings.
- Corrected import order.
- Removed an unnecessary `list()` call.
@greenc-FNAL
Copy link
Owner

@jules Please open a pull request with target Framework-R-D/phlex@main from this branch (feature-build-matrix-defaults), and close this pull request.

@google-labs-jules
Copy link
Author

@jules Please open a pull request with target Framework-R-D/phlex@main from this branch (feature-build-matrix-defaults), and close this pull request.

I understand. I have completed all the code changes on this branch. However, I am unable to open a pull request against a different repository. Please open the new pull request from the feature/build-matrix-defaults branch to Framework-R-D/phlex@main at your convenience.

@greenc-FNAL greenc-FNAL closed this Dec 2, 2025
@greenc-FNAL greenc-FNAL deleted the feature-build-matrix-defaults branch December 2, 2025 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant