Skip to content

chore: sync bounty board data - #218

Closed
github-actions[bot] wants to merge 1 commit into
stagingfrom
bot/bounty-sync
Closed

github-actions[bot] wants to merge 1 commit into
stagingfrom
bot/bounty-sync

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown

Regenerated src/data/bounties.generated.json from the bounty-labelled issues. Opened by the Sync bounty board data workflow.

Review the diff before merging — these are the rewards that go live on the public bounty board.

@github-actions
github-actions Bot requested a review from a team as a code owner August 2, 2026 23:00
@cla-bot

cla-bot Bot commented Aug 2, 2026

Copy link
Copy Markdown

We require contributors to sign our Contributor License Agreement, and we don"t have @github-actions[bot] on file. In order for us to review and merge your code, please visit https://www.arrowair.com/docs/contributing/cla and follow the instructions on the page to add yourself to the list.

@sl33ty

sl33ty commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Superseded by #219, which carries the identical bounties.generated.json content.

This PR cannot merge: the workflow commits as github-actions[bot], which fails verification/cla-signed and cannot produce a verified signature, both of which the base branch requires. #219 is the same diff recommitted under a CLA-covered, GPG-signed author.

Closing so the sync branch is free for the next dispatch. The workflow itself still needs fixing so this is not manual each time.

@sl33ty sl33ty closed this Aug 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant