feat(hiring): point merged candidates to open Goal/Problem/Bug issues

[HJKUNST]

Candidates whose profile PR is merged are pointed to open Goal,
Problem, and Bug issues, instead of a stale trial-task label filter.

Closes #1175

[holdex]

Time Submission Status

Member	#	Time	Running Total	Status	Last Update
HJKUNST			30min	✅ Submitted	Sep 2, 2026, 6:13 AM
zolotokrylin			-	⏳ Pending	-

---

Submit or update total time with:

@holdex pr submit-time 2h

Add time on top of previous submission with:

@holdex pr add-time 1h30m

See available commands to help comply with our Guidelines.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: b843cefe-b091-41c7-8369-1b6c9e43af69

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[HJKUNST]

@holdex pr submit-time 30m

[zolotokrylin]

@HJKUNST two guidelines to follow here.

Tag me explicitly when you need advice or have a question. Your question about switching the instruction to "leave a comment to claim", and the trial-task usage in scripts/rename-job-application-issues.mjs, sits in a review thread with no mention, so it does not reach me as something waiting on an answer. Put @zolotokrylin in the thread and it lands as a request I can act on. Ask as many questions as you need, that part is expected, it just has to be addressed to someone.

• https://github.com/holdex/developers/blob/main/docs/rules/DEV-130.md
• https://github.com/holdex/developers/blob/main/docs/rules/DEV-210.md

Re-request review once the work is ready. A push or a reply on a thread does not notify me and does not clear the review state, so the PR sits unseen. It is not ready right now: the inline comment threads are still unresolved. When they are resolved and every requested change is in, use GitHub's re-request review control on each reviewer.

• https://github.com/holdex/developers/blob/main/docs/rules/DEV-415.md

So either mention me on the thread if you want an answer first, or close out the open threads and re-request review.

[HJKUNST]

@zolotokrylin following up, three pull requests are ready and unreviewed, and two questions are open.

#1243, #1244 and #1245 all have their checks green: requesting a reviewer returns a permissions error from a fork, so a comment is the only signal I can send for those two.

#1163 and #1176 have questions waiting from the 2nd.
Requesting your review on all three, and an answer on the two questions.