Skip to content

De-hardcode discovery from gittensory's own conventions #4784

Description

@JSONbored

Problem: Discovery and claim logic assumes gittensory's own labels, issue templates, and scoring rubric.

Area: AMS / Miner

Proposal: Work through #4780's checklist, turning each hardcoded assumption into per-tenant configuration with gittensory's own conventions surviving only as the default.

Deliverables:

  • Discovery/claim code with no remaining hardcoded gittensory-specific assumption from the F2 checklist.

Acceptance criteria:

  • Every item on the F2 checklist is either resolved or explicitly deferred with a reason.
  • Existing behavior against gittensory's own repos is unchanged (regression-tested).

Test scenarios:

  • Full existing miner test suite passes unchanged.
  • A new test repo with different labels/templates is discoverable using its own configuration, not gittensory's defaults.

Resources:

  • The miner package's discovery and claim modules.

Boundaries:


Part of #4778.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.

    Projects

    Status
    Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions