feat(trial): receive the goal matching the role you applied for - #1218
feat(trial): receive the goal matching the role you applied for#1218zolotokrylin wants to merge 1 commit into
Conversation
|
@holdex pr submit-time 2h |
Time Submission Status
Submit or update total time with: Add time on top of previous submission with: See available commands to help comply with our Guidelines. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@holdex pr submit-time 2h |
The handover comment pointed every merged candidate at an open
trial-taskquery. That label is dead, and the five issues it returned were this
repository's own automation, matched to nobody's role.
The comment now names the open Goal carrying the application's
position/*label, by title and by link. When a role has no Goal yet, which is five of
them, the candidate is told a reviewer is picking one and the application gets
review-required, so the gap reaches a person instead of stopping at a deadlink.
Both merge paths post the same comment:
scripts/validate-profile.mjswhen thebot merges, and
job-application-reopen.jswhen a person does. The lookup andthe wording live in one new module,
.github/workflows/trial-goal.js, becausethe two templates drifting apart is how the dead link survived.
Verified against stubbed clients on both paths and both branches, and the label
query against the live API:
--dry-runnow prints the handover comment it would post, which it previouslystopped short of.