freecodexyz/free-code 0xE8134C7574469f4DdD807e456C4eF8De741F8eee

[paoloanzn]

Replace the title above with the repository you want to register and the wallet that should hold its
key, separated by a space. The body is ignored — only the title matters.

octocat/Hello-World 0x1111111111111111111111111111111111111111

You do not need any ETH, and you do not need to commit anything to the repository. Opening this
issue is the whole flow: a workflow here checks that you control the repository, requests a signed
proof from GitHub, and a relayer pays for the transaction.

Control is established in whichever of these applies first:

• You own it. Automatic for a repository owned by your own account.
• The fcf GitHub App is installed on it. One Metadata: read permission, installed once by an
  organisation owner. Required for private repositories.
• An admin added the challenge topic. If neither of the above applies, the workflow will comment
  with a one-off topic to add to the repository. Adding a topic needs admin permission, which is the
  point, and it can be removed as soon as registration completes.

The result is posted back as a comment on this issue.

[github-actions]

Could not establish that you control freecodexyz/free-code. Any one of these is enough:

• You own it. Works automatically for a repository owned by your own account.
• Install the fcf GitHub App on the repository. It asks for Metadata: read and nothing else, and is the only option for a private repository.
• Add this topic to the repository, then open a new issue. Setting a topic requires admin permission, and it can be removed once registration completes:

fcf-97cdf0e05be5e890eec7