Skip to content

trunk-merge/pr-643/1e0bdb21-1a33-4919-9abe-baf969b08e20#644

Closed
trunk-staging-io[bot] wants to merge 2 commits into
mainfrom
trunk-merge/pr-643/1e0bdb21-1a33-4919-9abe-baf969b08e20
Closed

trunk-merge/pr-643/1e0bdb21-1a33-4919-9abe-baf969b08e20#644
trunk-staging-io[bot] wants to merge 2 commits into
mainfrom
trunk-merge/pr-643/1e0bdb21-1a33-4919-9abe-baf969b08e20

Conversation

@trunk-staging-io
Copy link
Copy Markdown

Trunk Merge Pull Request Banner

This pull request was created and is being managed by Trunk Merge.

This pull request is based on the main branch at SHA 29618f8a2a476193b3b73ee0d331abfc761de443.

See more details here.

When CI completes, this pull request will be closed automatically.

Pull Requests Being Tested

This pull request is testing the changes from pull request 643.

samgutentag and others added 2 commits May 7, 2026 15:43
Pulls forward the small bits worth keeping from Eli's original Chrome
Extension docs PR, since the page itself has evolved well past that
draft via several subsequent merged PRs.

- Add a frontmatter description so GitBook renders proper metadata
- Add an inline pointer to the Submit and cancel pull requests
  reference page after the Submit steps, so readers can drill into
  the full lifecycle from this entry point
- Replace the FAQ link to a hard-coded GitHub commit URL with a
  relative path to getting-started, matching the rest of the docs

Closes the conflict-stale #588 in favor of these targeted edits on
top of the current main.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@trunk-staging-io trunk-staging-io Bot closed this May 7, 2026
@trunk-staging-io trunk-staging-io Bot deleted the trunk-merge/pr-643/1e0bdb21-1a33-4919-9abe-baf969b08e20 branch May 7, 2026 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant