The Situation
We currently have two separate GitHub Actions workflow files running when a Pull Request is opened:
welcome-bot.yml (Welcomes first-time contributors)
logic-verification.yml (Runs unit tests and verifies that 1 is still 1)
The Problem
Because our unit test suite runs lighting-fast, the Logic Verification CI workflow finishes running and comments ✅ Logic Verified! on the PR before the Welcome Bot finishes checking the user database and posting its welcome message.
Visually, this looks out of order in the PR timeline. The welcoming message should always appear first before the technical verification results layout.
The Goal
We want to ensure that the Welcome Bot always successfully posts its comment before the Logic Verification bot posts its success/failure message.
CRITICAL REQUIREMENT: We want to keep these as two separate YAML workflow files to maintain modularity. We do not want to combine them into a single file.
How to Contribute
- Fork the repository.
- Figure out a clean way to do it
- Open a Pull Request with your solution!
The Situation
We currently have two separate GitHub Actions workflow files running when a Pull Request is opened:
welcome-bot.yml(Welcomes first-time contributors)logic-verification.yml(Runs unit tests and verifies that 1 is still 1)The Problem
Because our unit test suite runs lighting-fast, the
Logic Verification CIworkflow finishes running and comments✅ Logic Verified!on the PR before theWelcome Botfinishes checking the user database and posting its welcome message.Visually, this looks out of order in the PR timeline. The welcoming message should always appear first before the technical verification results layout.
The Goal
We want to ensure that the
Welcome Botalways successfully posts its comment before theLogic Verificationbot posts its success/failure message.CRITICAL REQUIREMENT: We want to keep these as two separate YAML workflow files to maintain modularity. We do not want to combine them into a single file.
How to Contribute