Move gh-Based Automation to uf

Port release scripts, pull request tooling and webhook consumers written for the GitHub CLI, the GitHub REST API or GitHub webhooks, with every gap stated up front.

A migration aid, not a compatibility layer

This is a migration aid, not a compatibility layer. UnityFreak does not implement the GitHub REST API, GraphQL API, gh extensions or GitHub webhook payloads, and nothing here makes a script written for GitHub run unchanged. Each row says what carries over, what only partly carries over and what does not exist, so you can port a script deliberately.

1. What this is (and is not)

Each row below says what a gh command, a GitHub REST route or a GitHub webhook event maps to on UnityFreak, and how complete the mapping is.

SupportedA uf command or endpoint does the same job. Flags and output shapes can still differ; read the notes.
Partly supportedPart of the job is covered. The unsupported flags or fields are listed.
Not supportedThere is no equivalent in uf or in the headless API. The reason is given, with a workaround when one honestly exists.

This page is generated from the same table the uf migrate commands use. The markdown version lives in the repository at docs/migration/gh-to-uf.md.

2. The uf migrate tools

uf migrate map gh pr create                      # look up one gh command
uf migrate map --api GET /repos/OWNER/REPO/pulls # look up a GitHub REST route
uf migrate check release.sh                      # scan a script (never runs it)
uf migrate check release.sh --rewrite > release-uf.sh
uf migrate webhook --event push --repo OWNER/REPO < delivery.json

uf migrate check is text matching, not a parser. It can miss a call built at run time and can flag text in a comment, so a clean report is not proof that a script is migrated. It reads the file and never executes it; --rewrite prints a translated copy and never edits the original.

Signing in for repository work: uf auth login --repos. Repository commands are described in the CI guide for the statuses and check runs your external CI reports.

3. gh commands

gh commands, their mapping status and the uf command to use
gh command	Status	On UnityFreak
`gh auth login`	Partly supported	`uf auth login --repos` Add --repos so the token carries repo:read/repo:write. There is no gh-style credential helper installation: uf passes the token to git per command and never stores it for plain git use. Flags with no uf equivalent (5) `--with-token`: uf has no stdin token login; export UF_TOKEN=<API key> for non-interactive use `--web`: uf login always uses the browser device-code flow (use --headless to print the code instead) `--hostname`: set UF_BASE_URL to point uf at another UnityFreak host `--git-protocol`: uf repo clone chooses HTTPS or --ssh per call `--scopes`: uf requests fixed scopes; add --repos for repository access and --read-only to drop writes
`gh auth status`	Supported	`uf auth status` Reports the account, scopes and expiry of the saved credential.
`gh auth token`	Not supported	uf never prints a saved token. Create an API key in Settings -> API Keys and export it as UF_TOKEN when a script needs one.
`gh repo clone OWNER/REPO [DIR]`	Supported	`uf repo clone OWNER/REPO [DIR]` uf runs your own git; HTTPS needs git 2.31+. Extra git flags after -- are not passed through; --branch and --depth are available. Flags with no uf equivalent (2) `-u`: uf repo clone does not add an upstream remote for forks `--upstream-remote-name`: uf repo clone does not add an upstream remote for forks
`gh repo create NAME`	Partly supported	`uf repo create NAME` Visibility defaults to private on both. Flags with no uf equivalent (16) `-s`: uf cannot create a repository from a local directory (--source); create it, then git remote add and git push `--source`: uf cannot create a repository from a local directory; create it, then git remote add and git push `--push`: uf repo create does not push; run git push yourself `-r`: no --remote flag on create `--remote`: no --remote flag on create `-g`: no .gitignore templates on create (the --template starters carry their own) `--gitignore`: no .gitignore templates on create (the --template starters carry their own) `-p`: gh --template means a template REPOSITORY; uf --template is a built-in starter id (general, unity, unreal). Template repositories are not available in the CLI `--template`: gh --template means a template REPOSITORY; uf --template is a built-in starter id (general, unity, unreal). Template repositories are not available in the CLI `-h`: no homepage field `--homepage`: no homepage field `--team`: uf takes an organization id with --org, not a team `--disable-issues`: set in repository settings `--disable-wiki`: set in repository settings `--include-all-branches`: only applies to template repositories `-t`: uf takes an organization id with --org, not a team An organization-owned repository is `uf repo create NAME --org ORG_ID` (UnityFreak takes the organization id, not `ORG/NAME`). License ids are lower case: mit, apache-2.0, gpl-3.0, bsd-3-clause, unlicense.
`gh repo view OWNER/REPO`	Partly supported	`uf repo view OWNER/REPO` Prints visibility, default branch and clone URLs; it does not render the README. Flags with no uf equivalent (5) `-w`: no --web `--web`: no --web; open the repository in the browser `--jq`: pipe uf --json into jq `-q`: pipe uf --json into jq `-b`: no --branch on view
`gh repo list`	Partly supported	`uf repo list` Lists the repositories you own or can access (paged; --page N). `gh repo list OWNER` for another owner is not supported. Flags with no uf equivalent (6) `--jq`: pipe uf --json into jq `--language`: not filterable `--topic`: not filterable `--archived`: not filterable `--source`: not filterable `--fork`: not filterable
`gh repo fork`	Not supported	Forks exist in the web app, but there is no fork command in uf and no fork endpoint in the headless API.
`gh repo edit \| delete \| archive \| rename \| sync \| set-default`	Not supported	Repository administration is in the web app (Settings). uf covers create, view, list and clone only.
`gh pr create`	Partly supported	`uf pr create` Head and base default from the current branch (its upstream's name) and the repository default branch. Flags with no uf equivalent (20) `-r`: reviewers cannot be requested from uf; use the web app `--reviewer`: reviewers cannot be requested from uf; use the web app `-a`: no assignees on pull requests `--assignee`: no assignees on pull requests `-l`: labels cannot be set from uf; use the web app `--label`: labels cannot be set from uf; use the web app `-m`: no milestones `--milestone`: no milestones `-p`: no projects flag `--project`: no projects flag `-w`: no --web `--web`: no --web `-T`: no pull request templates flag `--template`: no pull request templates flag `--fill-first`: uf uses the last commit only `--fill-verbose`: uf uses the last commit only `--no-maintainer-edit`: no such setting `-e`: uf has no editor mode; pass --title/--body `--editor`: uf has no editor mode; pass --title/--body `--recover`: not supported Pull requests from a fork (--head OWNER:BRANCH) are not supported by uf; use the web app. The head branch must already be pushed; uf does not push for you.
`gh pr list`	Partly supported	`uf pr list` Newest first, 25 per page by default. Flags with no uf equivalent (17) `-a`: no author filter `--author`: no author filter `-A`: no assignee filter `--assignee`: no assignee filter `-l`: no label filter in uf `--label`: no label filter in uf `-B`: no base filter `--base`: no base filter `-H`: no head filter `--head`: no head filter `-S`: no search `--search`: no search `--jq`: pipe uf --json into jq `-q`: pipe uf --json into jq `-w`: no --web `--web`: no --web `--draft`: no draft filter gh --state accepts open\|closed\|merged\|all; uf --status accepts open\|merged\|closed (no all).
`gh pr view NUMBER`	Partly supported	`uf pr view NUMBER` Takes a pull request NUMBER only (not a branch name or URL). Flags with no uf equivalent (6) `-c`: comments are not shown `--comments`: comments are not shown `-w`: no --web `--web`: no --web `--jq`: pipe uf --json into jq `-q`: pipe uf --json into jq
`gh pr checks [NUMBER]`	Supported	`uf pr checks [NUMBER]` Lists check runs and commit statuses for the pull request's head commit. --watch polls with backoff and gives up after --watch-timeout seconds. Flags with no uf equivalent (6) `--fail-fast`: uf --watch always waits for every check `--required`: uf does not distinguish required checks in the output `-w`: no --web `--web`: no --web `--jq`: pipe uf --json into jq `-q`: pipe uf --json into jq EXIT CODES DIFFER: gh exits 1 when a check fails and 8 while checks are pending; uf exits 8 when a check fails and 9 while checks are pending (0 means all passing or none reported). Review any `$? -eq 1` / `-eq 8` test.
`gh pr merge`	Not supported	Merging runs the repository's merge gates (required checks, approvals, rulesets, merge queue, bypass reasons). uf does not expose that flow; merge in the web app.
`gh pr review \| comment \| close \| reopen \| ready \| edit \| diff \| checkout \| status \| update-branch \| lock`	Not supported	Only create, list, view and checks exist in uf. Reviews, comments, labels and state changes are in the web app.
`gh issue list \| create \| view \| comment \| close \| edit ...`	Not supported	`uf issue` is a synonym for `uf task` (project-management tasks), a different system from a repository's own issues. Repository issues are in the web app only. If you are moving to UnityFreak project management, `uf task list\|create\|view\|comment` is the nearest equivalent, with different fields.
`gh release create TAG [FILES...]`	Partly supported	`uf release create TAG [FILES...]` Publishes unless --draft is given. Flags with no uf equivalent (8) `--generate-notes`: uf does not generate release notes `--notes-from-tag`: not supported `--target`: uf releases an EXISTING tag; create and push the tag first (git tag / git push) `--discussion-category`: no discussions `--latest`: no 'latest' marker `--verify-tag`: uf always requires the tag to exist `--notes-start-tag`: no --notes-start-tag `--fail-on-no-commits`: uf does not compare commits since the last release The tag must already exist in the repository; gh can create it from --target, uf cannot. Files are attached while the release is a draft and the release is published afterwards (a published release's files are frozen). Files print their SHA-256. Per-file limit 500 MiB, 20 files per release; executable and script types (.exe .sh .js .html .svg ...) are refused. gh `FILE#label` display labels are not supported.
`gh release upload TAG FILES...`	Supported	`uf release upload TAG FILES...` Re-running is safe: a file already attached with the same checksum is skipped, and the server keeps one file per name in a release. After a dropped connection uf waits and polls for up to about 30 seconds before it re-sends. uf creates a DRAFT release if there is none and leaves it a draft unless you add --publish. If the release is already published its files are frozen: uf stops unless you add --reopen (unpublish, upload, publish again; the signed checksums manifest is regenerated). gh `FILE#label` display labels are not supported.
`gh release list`	Partly supported	`uf release list` Flags with no uf equivalent (5) `--exclude-drafts`: not filterable `--exclude-pre-releases`: not filterable `--order`: not sortable `--jq`: pipe uf --json into jq `-q`: pipe uf --json into jq
`gh release view TAG`	Partly supported	`uf release view TAG` A TAG is required (no 'latest' lookup). Flags with no uf equivalent (4) `-w`: no --web `--web`: no --web `--jq`: pipe uf --json into jq `-q`: pipe uf --json into jq
`gh release download \| delete \| delete-asset \| edit \| verify`	Not supported	uf can create, upload, list and view releases. Downloading, editing and deleting are in the web app; downloads are served as time-limited signed URLs.
`gh workflow list \| view \| run \| enable \| disable ; gh run list \| view \| watch \| rerun \| cancel \| download \| delete`	Not supported	UnityFreak has no native workflow runner (native CI is outside the current release). You keep your external CI and it reports commit statuses and check runs to UnityFreak (see /help/ci). `uf pr checks --watch` replaces watching a run's result on a pull request; triggering, re-running and cancelling runs stays in your CI system.
`gh api ENDPOINT`	Not supported	uf has no generic API passthrough and UnityFreak does not accept GitHub API paths. Look the endpoint up in the endpoint table (`uf migrate map --api METHOD PATH`) and call the documented UnityFreak route, or use a dedicated uf command.
`gh gist \| codespace \| extension \| alias \| secret \| variable \| label \| search \| ruleset \| cache \| attestation \| ssh-key \| gpg-key \| project \| browse \| status \| config`	Not supported	None of these have a uf command. Labels, SSH/GPG keys, rulesets and project boards are managed in the web app; Actions secrets and variables belong to your external CI; gists, codespaces and gh extensions do not exist on UnityFreak.

4. GitHub REST routes

UnityFreak does not implement the GitHub REST API. The routes under /api/cli/v1 are the headless, API-key-only ones the uf CLI uses; send Authorization: Bearer <API key> with a key that carries the listed scope.

GitHub REST routes, their mapping status and the UnityFreak route to use
GitHub route	Status	On UnityFreak
`GET /repos/{owner}/{repo}`	Supported	`GET /api/cli/v1/repos/{owner}/{repo}` Scope: `repo:read` Different JSON shape (cloneUrl, sshCloneUrl, defaultBranch, visibility). Authenticate with Authorization: Bearer <API key>.
`GET /user/repos`	Partly supported	`GET /api/cli/v1/repos` Scope: `repo:read` Page-based (?page=&limit=, max 100) and returns { repos, total, page, limit }. Other users' repositories (/users/{u}/repos, /orgs/{o}/repos) are not available.
`POST /user/repos`	Partly supported	`POST /api/cli/v1/repos` Scope: `repo:write` Body fields: name, slug, description, visibility (public\|private\|internal), orgId (the organization id, not its login), defaultBranch, initReadme, template, license. GitHub's private/auto_init/gitignore_template/has_issues fields are not accepted.
`GET /repos/{owner}/{repo}/pulls`	Partly supported	`GET /api/cli/v1/repos/{owner}/{repo}/pulls` Scope: `repo:read` Only ?status=open\|merged\|closed, ?page and ?limit; GitHub's head/base/sort/direction filters do not exist. Fields: number, title, status, isDraft, sourceBranch, targetBranch, author.username.
`POST /repos/{owner}/{repo}/pulls`	Partly supported	`POST /api/cli/v1/repos/{owner}/{repo}/pulls` Scope: `repo:write` Body: title, description (GitHub: body), sourceBranch (head), targetBranch (base), isDraft (draft). Fork heads (head: owner:branch) and maintainer_can_modify/issue are not supported.
`GET /repos/{owner}/{repo}/pulls/{number}`	Partly supported	`GET /api/cli/v1/repos/{owner}/{repo}/pulls/{number}` Scope: `repo:read` liveHeadSha is the branch tip now; headSha is the recorded head. GitHub's head.sha/base.sha/mergeable_state fields have different names.
`PUT /repos/{owner}/{repo}/pulls/{number}/merge`	Not supported	Merging is not exposed through the headless API; merge in the web app.
`* /repos/{owner}/{repo}/pulls/{number}/{reviews\|comments\|requested_reviewers\|files\|commits}`	Not supported	Reviews, comments, reviewer requests and diffs are available to the web app, not through the headless API.
`GET /repos/{owner}/{repo}/commits/{ref}/check-runs`	Partly supported	`GET /api/cli/v1/repos/{owner}/{repo}/commits/{sha}/check-runs` Scope: `repo:read` {sha} must be a full commit SHA (branch and tag names are not resolved). Returns { checkRuns: [...] } with name, status, conclusion, detailsUrl.
`GET /repos/{owner}/{repo}/commits/{ref}/status`	Partly supported	`GET /api/cli/v1/repos/{owner}/{repo}/statuses/{sha}` Scope: `repo:read` {sha} must be a full commit SHA. Returns { combinedState, statuses: [...] } with the latest status per context.
`POST /repos/{owner}/{repo}/statuses/{sha}`	Partly supported	`POST /api/v1/repos/{owner}/{repo}/statuses/{sha}` Scope: `repo:write` Reporting statuses from CI uses the existing CI endpoint, documented at /help/ci, not the uf CLI namespace. Body: state (pending\|success\|failure\|error), context, description, targetUrl (GitHub: target_url).
`POST /repos/{owner}/{repo}/check-runs`	Partly supported	`POST /api/v1/repos/{owner}/{repo}/check-runs` Scope: `repo:write` Documented at /help/ci/generic. Body: name, sha, status, conclusion, detailsUrl, output { title, summary, text, annotations[] }. Not every GitHub check-run field exists (no actions, images, external_id).
`GET /repos/{owner}/{repo}/releases`	Partly supported	`GET /api/cli/v1/repos/{owner}/{repo}/releases` Scope: `repo:read` Page-based; returns { releases, total, page, limit } with tagName, isDraft, isPrerelease and assets[] (fileName, sizeBytes, sha256Digest).
`POST /repos/{owner}/{repo}/releases`	Partly supported	`POST /api/cli/v1/repos/{owner}/{repo}/releases` Scope: `repo:write` Body: tagName (the tag must exist), name, body, isDraft, isPrerelease. GitHub's target_commitish, generate_release_notes, make_latest and discussion_category_name are not supported. Create it as a draft to attach files, then PATCH { isDraft: false }.
`PATCH /repos/{owner}/{repo}/releases/{release_id}`	Partly supported	`PATCH /api/cli/v1/repos/{owner}/{repo}/releases/{releaseId}` Scope: `repo:write` Fields: name, body, isDraft (false publishes, true unpublishes and clears the signed checksums manifest). {releaseId} is UnityFreak's release id, not the tag.
`POST https://uploads.github.com/repos/{owner}/{repo}/releases/{release_id}/assets?name=NAME`	Partly supported	`POST /api/cli/v1/repos/{owner}/{repo}/releases/{releaseId}/assets` Scope: `repo:write` multipart/form-data with one field named `file` (GitHub sends the raw bytes with ?name=). 201 means attached; 202 means held for the safety scan and NOT attached. 500 MiB per file, 20 per release, only while the release is a draft.
`DELETE /repos/{owner}/{repo}/releases/assets/{asset_id}`	Partly supported	`DELETE /api/cli/v1/repos/{owner}/{repo}/releases/{releaseId}/assets/{assetId}` Scope: `repo:write` The release id is part of the path.
`* /repos/{owner}/{repo}/labels[/...]`	Not supported	Labels are managed in the web app; there is no headless label endpoint.
`* /repos/{owner}/{repo}/issues[/...]`	Not supported	Repository issues are not in the headless API. (`/api/public/v1/tasks` is the project-management task API, a different system.)
`* /repos/{owner}/{repo}/hooks[/...]`	Not supported	Repository webhooks are created in the web app (Settings -> Webhooks); there is no headless webhook-management endpoint.
`* /repos/{owner}/{repo}/actions[/...]`	Not supported	There is no native workflow runner, so no workflow, run, artifact or dispatch endpoints. Your external CI reports statuses and check runs instead.
`* /repos/{owner}/{repo}/(contents\|git\|branches\|commits\|compare\|tags\|trees\|blobs)[/...]`	Not supported	Not in the headless API. Use git itself (clone/fetch) to read repository content.
`POST /graphql`	Not supported	UnityFreak has no GraphQL API.
`* /orgs/**`	Not supported	Organizations, users, teams, search, gists, the authenticated-user routes other than the repository list/create, GitHub App installation routes: not provided by the headless API.

5. Webhook headers

GitHub webhook delivery headers and the UnityFreak header to read instead
GitHub header	Status	On UnityFreak
`X-GitHub-Event`	Supported	`X-Webhook-Event` UnityFreak event names differ; see the event table. The event name is also the `event` field of the JSON body.
`X-GitHub-Delivery`	Supported	`X-Delivery-Id` A retry of the same delivery reuses the same id (use it to deduplicate). It is also the `deliveryId` field of the JSON body.
`X-Hub-Signature-256`	Supported	`X-Signature` Same scheme: `sha256=` plus the lower-case hex HMAC-SHA256 of the exact raw request body, keyed with the webhook secret. Compare in constant time. Verify over the raw bytes, not re-serialized JSON.
`X-Hub-Signature`	Not supported	UnityFreak signs with SHA-256 only; there is no SHA-1 signature.
`X-GitHub-Hook-ID, X-GitHub-Hook-Installation-Target-ID, X-GitHub-Hook-Installation-Target-Type`	Not supported	Not sent.

6. Webhook events

UnityFreak delivers eight repository webhook events, signed with HMAC-SHA256 like GitHub's. The payloads are smaller: the field lists below are exactly what is sent. uf migrate webhook reshapes a delivery into the GitHub layout for the fields that exist.

pushPartly supported

UnityFreak payload: { event, repoId, pusherUserId, updates: [{ ref, oldSha, newSha }], deliveryId }

One UnityFreak delivery can carry several ref updates; GitHub-shaped output has one object per update. The payload has no commit list, repository name or compare URL; fetch commits with git. Merge-queue candidate branches also produce push deliveries.

push payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`ref`	Supported	`updates[].ref`
`before`	Supported	`updates[].oldSha`
`after`	Supported	`updates[].newSha`
`created`	Partly supported	`updates[].oldSha` derived: true when oldSha is all zeros
`deleted`	Partly supported	`updates[].newSha` derived: true when newSha is all zeros
`forced`	Not supported	not reported
`commits`	Not supported	no commit list; run git log oldSha..newSha
`head_commit`	Not supported	not reported
`compare`	Not supported	not reported
`base_ref`	Not supported	not reported
`pusher.name`	Not supported	only the user id is sent
`pusher.email`	Not supported	only the user id is sent
`sender.id`	Partly supported	`pusherUserId` a UUID string, not a number
`sender.login`	Not supported	only the user id is sent
`repository.id`	Partly supported	`repoId` a UUID string, not a number
`repository.full_name`	Not supported	the payload does not name the repository; put it in the webhook URL (for example ?repo=owner/slug) or pass it to the converter
`repository.name`	Not supported	see repository.full_name
`repository.owner.login`	Not supported	see repository.full_name

jq recipe for the fields that carry over (delivery body on stdin):

jq -c '.updates[] | {ref, before: .oldSha, after: .newSha, created: (.oldSha | test("^0+$")), deleted: (.newSha | test("^0+$"))}'

pull_requestPartly supported

UnityFreak payload: { event, action, number, title, sourceBranch, targetBranch, authorId, fromFork, sourceRepo?, label?, deliveryId }

UnityFreak sends only the actions opened, synchronize, labeled and unlabeled. Closing, merging, reopening, editing, marking ready, assigning and review requests produce NO webhook: watch the target branch's push event to learn that a merge landed.

GitHub actions that send nothing on UnityFreak: closed, reopened, edited, ready_for_review, converted_to_draft, assigned, unassigned, review_requested, review_request_removed, auto_merge_enabled, auto_merge_disabled, enqueued, dequeued, locked, unlocked, milestoned, demilestoned, stacked.

pull_request payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`action`	Partly supported	`action` opened, synchronize, labeled, unlabeled only
`number`	Supported	`number`
`pull_request.number`	Supported	`number`
`pull_request.title`	Supported	`title`
`pull_request.head.ref`	Supported	`sourceBranch`
`pull_request.base.ref`	Supported	`targetBranch`
`pull_request.user.id`	Partly supported	`authorId` a UUID string, not a number
`pull_request.head.repo.full_name`	Partly supported	`sourceRepo.owner + '/' + sourceRepo.slug` only for a fork pull request; for a same-repository one the payload does not name the repository
`pull_request.head.repo.fork`	Partly supported	`fromFork` different meaning: on GitHub the head repository is itself a fork of something; on UnityFreak fromFork says the pull request comes from a fork of THIS repository (the converter sets fork true then, false otherwise)
`pull_request.draft`	Not supported	not in the payload; GET the pull request
`pull_request.body`	Not supported	not in the payload; GET the pull request
`pull_request.merged`	Not supported	no merge event
`pull_request.head.sha`	Not supported	not in the payload; GET the pull request (liveHeadSha)
`pull_request.base.sha`	Not supported	not in the payload
`pull_request.html_url`	Not supported	build it as https://<host>/<owner>/<slug>/pulls/<number>
`pull_request.labels`	Not supported	only the label being added or removed is sent (label)
`label.id`	Partly supported	`label.id` a UUID string, not a number
`label.name`	Supported	`label.name`
`label.color`	Supported	`label.color`
`repository.full_name`	Not supported	the payload does not name the repository; see push
`sender.login`	Not supported	only authorId (the pull request's author) is sent, not who performed the action

jq recipe for the fields that carry over (delivery body on stdin):

jq -c '{action, number, pull_request: {number, title, head: {ref: .sourceBranch}, base: {ref: .targetBranch}, user: {id: .authorId}}}'

issue_comment (UnityFreak: comment)Partly supported

UnityFreak payload: { event, pullRequestNumber, commentId, authorId, body, deliveryId }

UnityFreak's `comment` event is for pull request comments only and fires on creation only. It maps to GitHub's issue_comment on a pull request; line-anchored review comments (GitHub's pull_request_review_comment) are not told apart. Comments on repository issues send no webhook.

issue_comment payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`action`	Partly supported	always created
`comment.id`	Partly supported	`commentId` a UUID string, not a number
`comment.body`	Supported	`body`
`comment.user.id`	Partly supported	`authorId` a UUID string, not a number
`issue.number`	Supported	`pullRequestNumber`
`issue.pull_request`	Partly supported	derived: always present, because every comment event is on a pull request
`comment.user.login`	Not supported	only the user id is sent
`comment.html_url`	Not supported	not sent

jq recipe for the fields that carry over (delivery body on stdin):

jq -c '{action: "created", issue: {number: .pullRequestNumber, pull_request: {}}, comment: {id: .commentId, body, user: {id: .authorId}}}'

releasePartly supported

UnityFreak payload: { event, action, releaseId, tagName, name, isDraft, isPrerelease, authorId, deliveryId }

UnityFreak sends `created` (a release created directly as published) and `published` (a draft being published). Draft creation is silent. Edited, deleted, unpublished, prereleased and released produce no webhook.

GitHub actions that send nothing on UnityFreak: edited, deleted, unpublished, prereleased, released.

release payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`action`	Partly supported	`action` created or published only
`release.id`	Partly supported	`releaseId` a UUID string, not a number
`release.tag_name`	Supported	`tagName`
`release.name`	Supported	`name`
`release.draft`	Supported	`isDraft`
`release.prerelease`	Supported	`isPrerelease`
`release.author.id`	Partly supported	`authorId` a UUID string, not a number
`release.body`	Not supported	not in the payload; GET the release
`release.assets`	Not supported	not in the payload; GET the release
`release.target_commitish`	Not supported	not in the payload

jq recipe for the fields that carry over (delivery body on stdin):

jq -c '{action, release: {id: .releaseId, tag_name: .tagName, name, draft: .isDraft, prerelease: .isPrerelease}}'

statusSupported

UnityFreak payload: { event, sha, context, state, description, targetUrl, creatorId, deliveryId }

Fired for every commit status, including the status mirror of each check run and the platform's own native checks (creatorId null).

status payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`sha`	Supported	`sha`
`state`	Supported	`state`
`context`	Supported	`context`
`description`	Supported	`description`
`target_url`	Supported	`targetUrl`
`name`	Not supported	the converter fills it from the repository when given
`branches`	Not supported	not sent
`commit`	Not supported	not sent
`sender.id`	Partly supported	`creatorId` a UUID string, or null for a native check

jq recipe for the fields that carry over (delivery body on stdin):

jq -c '{sha, state, context, description, target_url: .targetUrl}'

createSupported

UnityFreak payload: { event, repoId, refType: 'branch'|'tag', ref, pusherUserId, sha, deliveryId }

create payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`ref`	Supported	`ref` the short name (no refs/heads/ prefix), as on GitHub
`ref_type`	Supported	`refType`
`master_branch`	Not supported	not sent
`description`	Not supported	not sent
`pusher_type`	Not supported	not sent

jq recipe for the fields that carry over (delivery body on stdin):

jq -c '{ref, ref_type: .refType}'

deleteSupported

UnityFreak payload: { event, repoId, refType, ref, pusherUserId, deliveryId }

delete payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`ref`	Supported	`ref`
`ref_type`	Supported	`refType`
`pusher_type`	Not supported	not sent

jq recipe for the fields that carry over (delivery body on stdin):

jq -c '{ref, ref_type: .refType}'

memberPartly supported

UnityFreak payload: { event, action, userId, username, role, previousRole?, deliveryId }

Collaborator added, edited (role change) or removed. Roles are UnityFreak's, not GitHub's permission names.

member payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`action`	Supported	`action`
`member.login`	Supported	`username`
`member.id`	Partly supported	`userId` a UUID string, not a number
`changes.permission.from`	Partly supported	`previousRole` UnityFreak role names; edited only
`role`	Partly supported	`role` no GitHub equivalent field; UnityFreak role name

jq recipe for the fields that carry over (delivery body on stdin):

jq -c '{action, member: {login: .username, id: .userId}}'

pingPartly supported

A test delivery is sent when you press Test in the webhook settings. It is not a subscribable event.

ping payload fields and where they come from on UnityFreak
GitHub field	Status	From UnityFreak field
`zen`	Not supported	not sent
`hook_id`	Not supported	not sent

check_run (UnityFreak: status)Not supported

There is no check_run webhook. A check run is mirrored as a commit status with the same name, so subscribe to `status` and treat context as the check name.

Events with no UnityFreak counterpartNot supported

GitHub: issues, pull_request_review, pull_request_review_comment, workflow_run, workflow_job, workflow_dispatch, deployment, deployment_status, fork, watch, star, repository, label, milestone, discussion, gollum, commit_comment, public, team, organization, installation, branch_protection_rule, code_scanning_alert, dependabot_alert, secret_scanning_alert, security_advisory, package, project, merge_group

UnityFreak delivers exactly eight repository webhook events: push, pull_request, comment, release, create, delete, status and member. Nothing else is sent, even for features that exist in the web app (issues, reviews, wiki).

7. What does not carry over

No GitHub REST/GraphQL compatibility: paths, field names and pagination differ, and most GitHub endpoints do not exist.
No generic `uf api` passthrough.
No native workflow runner; external CI reports statuses and check runs.
Pull request merge, review, comment and label operations are not in the CLI.
Repository issues are not in the CLI or the headless API.
Webhooks: eight events only, with smaller payloads than GitHub's.
Webhooks: UnityFreak sends pull_request only for opened, synchronize, labeled and unlabeled and release only for created and published; a merge, close or review produces NO webhook.

Move gh-Based Automation to uf

A migration aid, not a compatibility layer

1. What this is (and is not)

2. The uf migrate tools

3. gh commands

4. GitHub REST routes

5. Webhook headers

6. Webhook events

push◐Partly supported

pull_request◐Partly supported

issue_comment (UnityFreak: comment)◐Partly supported

release◐Partly supported

status✓Supported

create✓Supported

delete✓Supported

member◐Partly supported

ping◐Partly supported

check_run (UnityFreak: status)✕Not supported

Events with no UnityFreak counterpart✕Not supported

7. What does not carry over

Move gh-Based Automation to uf

A migration aid, not a compatibility layer

1. What this is (and is not)

2. The uf migrate tools

3. gh commands

4. GitHub REST routes

5. Webhook headers

6. Webhook events

push◐Partly supported

pull_request◐Partly supported

issue_comment (UnityFreak: comment)◐Partly supported

release◐Partly supported

status✓Supported

create✓Supported

delete✓Supported

member◐Partly supported

ping◐Partly supported

check_run (UnityFreak: status)✕Not supported

Events with no UnityFreak counterpart✕Not supported

7. What does not carry over

pushPartly supported

pull_requestPartly supported

issue_comment (UnityFreak: comment)Partly supported

releasePartly supported

statusSupported

createSupported

deleteSupported

memberPartly supported

pingPartly supported

check_run (UnityFreak: status)Not supported

Events with no UnityFreak counterpartNot supported

pushPartly supported

pull_requestPartly supported

issue_comment (UnityFreak: comment)Partly supported

releasePartly supported

statusSupported

createSupported

deleteSupported

memberPartly supported

pingPartly supported

check_run (UnityFreak: status)Not supported

Events with no UnityFreak counterpartNot supported