Skip to content

manual-github-actions.md

Latest commit

 

History

History
106 lines (74 loc) · 5.18 KB

manual-github-actions.md

File metadata and controls

106 lines (74 loc) · 5.18 KB
Raw

Manual GitHub Actions Checklist

Some GitHub profile actions are not exposed through the available API surface here. This file keeps them visible instead of pretending they were automated.

1. Pin RDLeader on the profile

Current API check still shows profile pins include Resume and do not include RDLeader. Re-checked on 2026-07-11 Asia/Shanghai with python3 scripts/check_profile_pins.py: the current GraphQL mutation surface exposes issue/comment/environment pin mutations and repository metadata mutations, but still does not expose a profile repository-pin mutation, so this remains a manual web-UI action. The checker now runs in CI as a report-only step; use python3 scripts/check_profile_pins.py --strict after the manual swap to make it fail until the recommended pinned set is visible. python3 scripts/check_manual_blockers.py --json now emits machine-readable nextActions, ownerActionRequired, and agentBlockedOnOwnerAction fields for handoff.

For the strongest technical first screen, replace Resume with RDLeader.

Recommended pinned set:

  1. qq-ai-bot
  2. RDLeader
  3. happydb
  4. go-service-starter
  5. go-http-middleware-kit
  6. CSAPPLabsAndNotes

Why:

  • qq-ai-bot = bot infrastructure flagship
  • RDLeader = agent-ops / control-plane flagship
  • happydb = Java/database internals proof
  • go-service-starter = Go backend service craft
  • go-http-middleware-kit = reusable Go library craft
  • CSAPPLabsAndNotes = systems fundamentals proof

Automation already completed around this item:

  • RDLeader project page exists: https://happysnaker.github.io/rdleader/.
  • RDLeader repository homepage now points to that project page.
  • RDLeader topics include agent-ops, control-plane, runtime-orchestration, sponsorware, and ai-workers.
  • The profile repo topics include agent-ops, oss-portfolio, and sponsorware.
  • Weekly profile CI now checks support-route, repository metadata, compact sponsor-release, operations-log, issue-label, share-kit, manual-blocker, README badge, and public site hygiene drift.
  • docs/flagship-technical-map.md now explains why RDLeader belongs in the first-screen technical proof set.
  • docs/share-kit.md and the live support page now expose proof-safe share snippets for qq-ai-bot and RDLeader.
  • The 10-second support router is live at https://happysnaker.github.io/support/#sponsor-router and is linked from profile, project pages, sponsor packet, share kit, support files, funding fallback, and live sponsor/support issues.
  • Default .github funding/support fallback now routes repositories without local support files through Tip / Proof / Review / Fund.
  • scripts/check_issue_labels.py keeps the manual/profile and sponsor/open-loop issues labeled for public triage.
  • scripts/check_ops_issue_log.py keeps happysnaker#2 as the append-only operations log now that the sponsor release is compact.

Manual path:

  1. Log in to GitHub as happysnaker in a real browser session.
  2. Open the GitHub profile page: https://github.com/happysnaker.
  3. Use the profile pins editor / Customize your pins UI.
  4. Remove Resume.
  5. Add RDLeader.
  6. Keep the other five pins unchanged.
  7. Save the pins.
  8. Run python3 scripts/check_profile_pins.py --strict and confirm the visible pins match the recommended list above.

Latest automation attempt: on 2026-07-12 UTC, the in-app browser session reached the public profile as logged-out (Sign in / Sign up visible), so the pin swap still requires an authenticated owner browser session.

2. Decide RDLeader license posture

Tracked in:

Current report command:

python3 scripts/check_rdleader_license.py

Before wider reuse/promotion, choose one of:

  • MIT
  • Apache-2.0
  • AGPL-style copyleft
  • Source-available for now

Do not imply unrestricted reuse until a license is published. The current share kit, sponsor release, support routes, and RDLeader support files intentionally preserve this caveat.

3. RDLeader public demo assets — completed

Tracked in:

Current status: completed with public-safe SVG demo assets, walkthrough video, browser walkthrough, fake-data reset path, onboarding guide, landing copy, distribution kit, and submission tracker. Keep future assets under the same safety rules:

  • no private paths;
  • no live group IDs;
  • no open IDs;
  • no message IDs;
  • no app IDs;
  • no QR onboarding artifacts;
  • no raw integration logs.

4. Review parked repos before promotion

Before promoting chinese-independent-developer, decide whether it should become a serious content asset or stay parked.

Minimum before promotion:

  • license decision
  • README positioning
  • support path
  • proof of maintenance intent

Tracking

This checklist is mirrored in happysnaker#1. Keep the issue and this file aligned when a manual item is completed. For the shortest owner-facing version, use owner-action-packet.md. Operational evidence belongs in happysnaker#2, not in the compact sponsor release body.