Triage: approve CI run on PR #162 (fork PR, first-time-contributor gate)

[danfulani0]

Triage: CI approval gate blocking PR #162 (fork PR, first-time contributor)

Hello @ApexChainx/maintainers — pinging the folks who can click "Approve and run workflows" on the Checks tab of #162.

What's blocking

This PR (closes #73, #92, #97 — assigned to @danfulani0) has zero workflow runs on it. Verified via the Actions API:

• GET /actions/runs?branch=fix/danfulani0-issues-92-97-73 → total_count = 0
• GET /commits/<sha>/check-runs → total_count = 0
• GET /repos/.../pulls/162 → mergeable_state: dirty (downstream of no CI, not a real conflict; git merge-tree against origin/main shows zero textual conflicts).

Why it's blocked

This is a cross-fork PR (danfulani0:fix/danfulani0-issues-92-97-73 → main) and the repo's CI workflows use on: pull_request, not pull_request_target. Public repos in this configuration typically require a maintainer to click "Approve and run workflows" once before fork PRs can run.

What I (the PR author) tried (all 403)

• gh run rerun — needs Actions: Write upstream.
• gh workflow run ci.yml --ref <branch> — and ci.yml has no workflow_dispatch trigger anyway.
• gh pr comment 162 (addComment) — danfulani0's integration scope is too narrow.

What a maintainer needs to do (≈ 1 click)

Open #162 → Checks tab → click "Approve and run workflows".

Once ci.yml queues and the failing step is visible, I can ship a targeted patch commit on the same branch fix/danfulani0-issues-92-97-73.

Optional faster path

If you'd rather skip the gate, a maintainer can merge the PR against a tracking-upstream branch (e.g. merge/162) from ApexChainx/main. That fires the push event workflows on the upstream branch and the logs are visible without the gate.

No code changes are needed here — only a single UI click on PR #162. Thanks!

[ahmadogo]

@ahmadogo has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Good day

I have read the requirements of this issue and i am confident that i can solve this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ahmadogo to this issue.

[drips-wave]

Congratulations, @ahmadogo! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @ahmadogo: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@ahmadogo's PR #303 was approved and merged by @usmanimamu17-create.

🏆 @ahmadogo: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (872 total points). Track your full progress on GrantFox.

👏 Great work, @ahmadogo! Keep contributing to ApexChainx.

[drips-wave]

This issue has been completed by @ahmadogo as part of the Stellar Wave Program's 7th Wave 🥳

😎 @ahmadogo: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.