Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: update path-filter job condition in ci.yml #2801

Merged
merged 1 commit into from
Jul 18, 2024
Merged

Conversation

ogabrielluiz
Copy link
Contributor

The path-filter job condition in ci.yml has been updated to include an additional check for the 'workflow_dispatch' event. This change ensures that the job runs when the event is triggered manually, in addition to when the pull request is approved or when it is not a draft PR. The updated condition improves the flexibility and coverage of the path-filter job.

The path-filter job condition in ci.yml has been updated to include an additional check for the 'workflow_dispatch' event. This change ensures that the job runs when the event is triggered manually, in addition to when the pull request is approved or when it is not a draft PR. The updated condition improves the flexibility and coverage of the path-filter job.
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jul 18, 2024
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jul 18, 2024
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2801.dmtpw4p5recq1.amplifyapp.com

@ogabrielluiz ogabrielluiz enabled auto-merge (squash) July 18, 2024 16:55
@ogabrielluiz ogabrielluiz changed the title refactor: update path-filter job condition in ci.yml ci: update path-filter job condition in ci.yml Jul 18, 2024
@ogabrielluiz ogabrielluiz enabled auto-merge (squash) July 18, 2024 16:55
Copy link
Contributor

Pull Request Validation Report

This comment is automatically generated by Conventional PR

Whitelist Report

Whitelist Active Result
Pull request is a draft and should be ignored
Pull request is made by a whitelisted user and should be ignored
Pull request is submitted by a bot and should be ignored
Pull request is submitted by administrators and should be ignored

Result

Pull request does not satisfy any enabled whitelist criteria. Pull request will be validated.

Validation Report

Validation Active Result
All commits in this pull request has valid messages
Pull request does not introduce too many changes
Pull request has a valid title
Pull request has mentioned issues
Pull request has valid branch name
Pull request should have a non-empty body

Result

Pull request satisfies all enabled pull request rules.

Last Modified at 18 Jul 24 16:58 UTC

@github-actions github-actions bot added the refactor Maintenance tasks and housekeeping label Jul 18, 2024
@ogabrielluiz ogabrielluiz merged commit 66e6370 into main Jul 18, 2024
14 checks passed
@ogabrielluiz ogabrielluiz deleted the ci/improveconds branch July 18, 2024 16:58
@github-actions github-actions bot added refactor Maintenance tasks and housekeeping and removed refactor Maintenance tasks and housekeeping labels Jul 18, 2024
nicoloboschi pushed a commit to datastax/ragstack-ai-langflow that referenced this pull request Jul 30, 2024
refactor: update path-filter job condition in ci.yml

The path-filter job condition in ci.yml has been updated to include an additional check for the 'workflow_dispatch' event. This change ensures that the job runs when the event is triggered manually, in addition to when the pull request is approved or when it is not a draft PR. The updated condition improves the flexibility and coverage of the path-filter job.

(cherry picked from commit 66e6370)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm This PR has been approved by a maintainer refactor Maintenance tasks and housekeeping size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants