Open your first pull request

Before you start

Signed up, then approved.

You must have signed up and received approval before you can contribute. Approval gives you organization membership and read-only access to Relay. Approvals are currently closed by a launch gate; sign-ups queue.

The workflow

From access to an open PR.

1. Sign in to GitHub CLI

   Install Git and GitHub CLI, then sign in with the GitHub account that was approved.

   gh auth login --git-protocol https

2. Fork Relay — this is required

   Your Relay access is read-only, so you cannot push branches to Relay itself. Fork it, keep that fork private, and do all branch work there. Do not create a public mirror.

   gh repo fork dangerously-skip-permissions/relay --clone
   cd relay
   git remote -v

3. Set your commit identity and start a branch

   Use the identity you want recorded on your commits. Then update your fork from Relay’s main and create a branch for one bounded change.

   git config user.name "Your Name"
   git config user.email "your-github-email@example.com"
   git switch main
   git pull --ff-only upstream main
   git push origin main
   git switch -c my-change

4. Make, inspect, commit, and push the change

   Make and test the change. Stage named paths, inspect what is staged, then push only to your fork branch.

   git add path/to/file
   git diff --cached
   git commit -m "Describe the change"
   git push -u origin my-change

5. Open the pull request into Relay main

   Use the browser flow so GitHub loads the required pull-request template. Complete the template before opening the PR.

   gh pr create --repo dangerously-skip-permissions/relay --base main --web

When you open a PR

It starts review. It transfers nothing.

PR body required

Complete every provenance field.

The PR body must include the required reaffirmation statement and every field below. A blocking check fails the pull request while any field is blank. Where nothing applies, enter none.

• Background materials.
• Third-party and open-source materials, with source, version, and license.
• AI assistance.
• Confidential or third-party proprietary input given to an AI tool.
• Any CT-3.5 section 7.4 authorization.

Working with an AI agent

The rules travel with the code.

Most contributors will use a coding agent. An agent that does not know these rules may fill the provenance block with plausible invention. So the rules ship inside the repository and are not tied to any one tool: when you fork Relay you also get AGENTS.md, which Codex, opencode, Cursor, Kilo and others read at the start of every session, and .agents/skills/ for the full detail. There is nothing to install.

The hard prohibitions are stated in AGENTS.md itself rather than behind a link, because an agent may read that file and nothing else. They apply in Relay and in your fork of it, and they add to your own agent configuration rather than replacing it.

• dspy-contribute — the workflow: fork, branch, pull request.
• dspy-provenance — how to fill the provenance block honestly.
• dspy-boundaries — what an agent must never do here.

An agent may draft provenance details, but it must identify its own involvement and must not invent human review. Maintainers use the written disclosures, pull-request diff, automated checks, and peer review instead of a duplicate self-assessment checklist.

Read the skills on GitHub → (visible once your access is approved)