Refactor CI workflow for logic verification#86
Open
Pranav-MSK wants to merge 2 commits into
Open
Conversation
Updated workflow to trigger on completion of 'Welcome Bot' and modified steps for repository checkout and comment posting. Signed-off-by: Pranav M S Krishnan <pranavmskrishnan@gmail.com>
✅ Logic Verified!The Automated Logic Suite has confirmed that 1 is still 1.
You are safe to merge this chaos. |
Signed-off-by: Pranav M S Krishnan <pranavmskrishnan@gmail.com>
✅ Logic Verified!The Automated Logic Suite has confirmed that 1 is still 1.
You are safe to merge this chaos. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updated workflow to trigger on completion of 'Welcome Bot' and modified steps for repository checkout and comment posting.
Description
Updated the
Logic Verification CIworkflow to trigger on the completion of theWelcome Botworkflow using theworkflow_runevent. This ensures a deterministic execution order where the welcome message is guaranteed to appear before technical verification results, resolving the race condition in the PR timeline. I have also updated the checkout and commenting steps to pull context directly from the triggering workflow.Closes #85
Type of Change
Checklist
Overengineering Verification
Validation
pytestpasses locally with no failuresTraceability
General
Screenshots (if applicable)
Additional Notes
The shift from
pull_request_targettoworkflow_runrequired explicitly mapping the PR number and head SHA from the triggering event context, as these are no longer implicitly available in the job environment.