GitHub Action for External Repos to Post Bounties

[sepulchralvoid666]

Bounty #855 — GitHub Action for External Repos to Post Bounties

What

A reusable GitHub Action that external repositories can install to automatically convert labeled GitHub issues into SolFoundry bounties.

Features

• Label detection: Triggers on issues.labeled event when the configured label (default: bounty) is added
• Simple YAML config: All settings via with: inputs — no extra config files
• Customizable reward tiers: Default reward, tier, deadline, and skills configurable at the workflow level
• Per-issue overrides: Authors can add an HTML comment to override defaults per issue:

  <!-- solfoundry: reward=1000000 tier=t1 skills=rust,backend deadline=14 -->
  

• Auto-comment: Posts a comment on the issue with a link to the created bounty
• Dry-run mode: Test the action without actually creating bounties
• Built with @actions/core + @actions/github: Standard GitHub Actions toolkit
• Compiled via ncc: Single bundled dist/index.js for reliable execution

Files

• actions/bounty-poster/action.yml — Action metadata and inputs
• actions/bounty-poster/src/index.ts — Main action logic
• actions/bounty-poster/src/types.ts — Internal types
• actions/bounty-poster/dist/ — Compiled bundle
• actions/bounty-poster/examples/workflow.yml — Example workflow
• actions/bounty-poster/README.md — Usage docs

Acceptance Criteria

• Simple YAML configuration for workflow setup
• Label detection and bounty auto-posting
• Customizable reward tiers and thresholds
• Per-issue override support

Closes #855

Solana wallet for payout: 9PmjWFwM2mdnjBNjJyfNMTWGCnGAKFpywsLF9xcRF8PK

[nagiexplorer88]

This action can create duplicate bounties after the first bounty label is added.

The workflow triggers on every issues.labeled event, but the code only checks whether the issue currently has the configured label:

if (!labels.includes(bountyLabel)) {
  core.info(`Issue #${issue.number} does not have label "${bountyLabel}" — skipping.`);
  return;
}

So if an issue already has bounty and someone later adds another label such as frontend or priority, the action runs again, sees that bounty is still present in issue.labels, and posts a second SolFoundry bounty for the same issue.

Since #855 is specifically for converting issues when the configured bounty label is added, this should check the event label itself, e.g. context.payload.label?.name === bountyLabel, before creating the bounty. That keeps later unrelated label changes from duplicating the bounty.