ci: workflows are triggered if pr name is edited #2872
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Made a small change to the github workflow such that the jobs are triggered if a PR is edited (for example the title). This makes it easier to change the title to conform to the new linting rules.
Greptile Overview
Updated On: 2025-10-07 12:44:33 UTC
Summary
This PR makes a minimal but purposeful change to the GitHub Actions workflow configuration to improve developer experience when working with PR title requirements. The change adds 'edited' to the list of pull request event types that trigger the `tidy3d-python-client-tests.yml` workflow.The workflow includes a 'lint-branch-name' job that enforces Jira key requirements by checking both branch names and PR titles as a fallback mechanism. Prior to this change, if a developer created a PR with a branch name lacking a Jira key, they would need to either create a new branch or close and reopen the PR to trigger the workflow validation after updating the PR title. Now, developers can simply edit their PR title to include the required Jira key, and the workflow will automatically re-run to validate compliance.
This change integrates seamlessly with the existing workflow infrastructure, maintaining all current functionality while reducing friction for developers who need to comply with the repository's commit linting rules. The modification aligns with the codebase's emphasis on developer productivity and automated quality checks.
Important Files Changed
Changed Files
Confidence score: 5/5
Sequence Diagram
sequenceDiagram participant User participant GitHub participant WorkflowEngine as "Workflow Engine" participant DetermineScope as "determine-test-scope" participant Lint as "lint" participant BranchLint as "lint-branch-name" participant CommitLint as "lint-commit-messages" participant SchemaVerify as "verify-schema-change" participant LocalTests as "local-tests" participant RemoteTests as "remote-tests" participant PRRequirements as "pr-requirements-pass" User->>GitHub: "Edit PR (title/description)" GitHub->>WorkflowEngine: "Trigger workflow on 'edited' event" WorkflowEngine->>DetermineScope: "Start determine-test-scope job" DetermineScope->>GitHub: "Check PR approval status" GitHub-->>DetermineScope: "Return approval state" DetermineScope->>DetermineScope: "Determine local_tests and remote_tests flags" DetermineScope-->>WorkflowEngine: "Output test scope decisions" par Parallel execution WorkflowEngine->>Lint: "Start linting (if tests enabled)" Lint->>Lint: "Run ruff format and check" Lint-->>WorkflowEngine: "Linting results" and WorkflowEngine->>BranchLint: "Start branch name linting" BranchLint->>BranchLint: "Check branch name and PR title for Jira key" BranchLint-->>WorkflowEngine: "Branch lint results" and WorkflowEngine->>CommitLint: "Start commit message linting" CommitLint->>CommitLint: "Check commit message format" CommitLint-->>WorkflowEngine: "Commit lint results" and WorkflowEngine->>SchemaVerify: "Start schema verification" SchemaVerify->>SchemaVerify: "Regenerate and verify schemas" SchemaVerify-->>WorkflowEngine: "Schema verification results" and WorkflowEngine->>LocalTests: "Start local tests (if enabled)" LocalTests->>LocalTests: "Run test suite with coverage" LocalTests-->>WorkflowEngine: "Local test results" and WorkflowEngine->>RemoteTests: "Start remote tests (if approved)" RemoteTests->>RemoteTests: "Run tests on multiple platforms" RemoteTests-->>WorkflowEngine: "Remote test results" end WorkflowEngine->>PRRequirements: "Start requirements check" PRRequirements->>PRRequirements: "Validate all required jobs passed" PRRequirements-->>GitHub: "Final workflow status" GitHub-->>User: "Workflow completion notification"Context used:
Rule from
dashboard- When implementing Jira key enforcement for pull requests, provide a fallback to check the PR title i... (source)