redhat-developer / redhat-developer/rhdh-fullsend
Track rhdh-plugins gaps against the rhdh-agentic Fullsend reference install
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 2
- Forks
- 7
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 8
Description
Context
rhdh-agentic is the QE/reference installation for Fullsend. The
rhdh-plugins runtime installation should follow it instead of carrying
repository-local workflow, harness, or agent customizations. Repository-specific
trigger scope and contributor guidance may remain alongside that installation.
The synchronization work in
rhdh-plugins#3740
removed the old runtime overrides and established which previous capabilities
are now provided centrally or through portable repository guidance.
Resolved discrepancies
- Public-repository command authorization: Fullsend v0.30.0 performs the
collaborator permission check in the managed reusable dispatcher. Slash
commands require repository write access, so the old repository-local shim
gate is no longer needed. - Selective pull-request scope:
rhdh-pluginsretains
pull_request_target.pathsrestrictions forworkspaces/boost/**,
workspaces/scorecard/**, andworkspaces/ai-integrations/**. - RHDH monorepo workspace routing:
rhdh-pluginsprovides a portable
repository skill at.agents/skills/rhdh-workspace/SKILL.md, exposed through
.claude/skills. A minimal Fullsend instruction file requires agents to use
it for workspace work. - Lingering Jest processes:
.fullsend/AGENTS.mdrequires non-interactive
Jest execution and explicitTaskStopcleanup for auto-backgrounded
verification commands, following #26.
Remaining discrepancy
- Stale fix-branch handling: the old installation rebased and force-pushed
the PR branch before fix runs. The reference installation intentionally has no
repository-owned rebase hook, so fix runs may still start from a stale branch.
Desired outcome
- Decide whether stale fix-branch handling belongs in Fullsend core, the shared
agents repository, or therhdh-fullsendinstallation blueprint. - Implement it centrally rather than restoring a repository-specific hook.
- Validate the change in
rhdh-agenticbefore promoting it torhdh-plugins.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the current rhdh-agentic reference installation with rhdh-plugins, including .fullsend/AGENTS.md and .agents/skills/rhdh-workspace/SKILL.md. Trace the former fix-branch rebase behavior and decide whether it belongs in Fullsend core, the shared agents repository, or the rhdh-fullsend blueprint. Done means the behavior is implemented centrally and validated in rhdh-agentic before promotion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ai-infra-agents, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100