Skip to content

Remove stray backticks from Windows installer README code blocks#9691

Merged
kevinchevalier merged 1 commit intowarpdotdev:masterfrom
BennyWaitWhat:bennywaitwhat/fix-windows-installer-codeblocks
May 1, 2026
Merged

Remove stray backticks from Windows installer README code blocks#9691
kevinchevalier merged 1 commit intowarpdotdev:masterfrom
BennyWaitWhat:bennywaitwhat/fix-windows-installer-codeblocks

Conversation

@BennyWaitWhat
Copy link
Copy Markdown
Contributor

Description

Fixes a copy-paste hazard in script/windows/README.md. Two iscc / .exe examples each ended with a trailing `. inside their ```shell fenced blocks:

 ```shell
-iscc .\script\windows\windows-installer.iss`.
+iscc .\script\windows\windows-installer.iss
```diff
 ```shell
-.\script\windows\Output\Warp-Windows-Setup.exe`.
+.\script\windows\Output\Warp-Windows-Setup.exe

Inside a fenced code block those characters render literally, so anyone copying the example commands into cmd.exe or PowerShell hits a syntax error from the trailing `` ` ``. Most likely a leftover from when the lines were in prose form (inline code closing a sentence) before being wrapped in code fences.

Verified the pattern is isolated to these two lines: `grep -rn '\`\.$'` across all repo Markdown files inside ```` ```shell ```` blocks returns zero other instances.

## Testing

Docs-only change; no test impact. The diff is purely the removal of two stray characters per line.

## Agent Mode

- [ ] Warp Agent Mode - This PR was created via Warp's AI Agent Mode

Two `iscc` / `.exe` examples in `script/windows/README.md` ended with
a trailing `` `. `` inside their ```shell fences. Inside a code block
those characters are literal, so anyone copy-pasting the example into
cmd.exe or PowerShell would hit a syntax error. Likely a leftover from
when the lines were in prose form (with inline-code backticks closing
a sentence) before being wrapped in code fences.
@cla-bot cla-bot Bot added the cla-signed label Apr 30, 2026
@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented Apr 30, 2026

@BennyWaitWhat

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I reviewed this pull request and requested human review from: @warpdotdev/oss-maintainers.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This docs-only PR removes stray trailing backticks from two Windows installer README shell examples so the commands can be copied without syntax errors.

Concerns

  • No correctness, security, or maintainability concerns found in the changed lines.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@kevinchevalier kevinchevalier self-requested a review May 1, 2026 15:25
Copy link
Copy Markdown
Contributor

@kevinchevalier kevinchevalier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making this change!

@kevinchevalier kevinchevalier merged commit 7784428 into warpdotdev:master May 1, 2026
27 checks passed
captainsafia added a commit to warpdotdev/oz-for-oss that referenced this pull request May 1, 2026
…lures in progress comment (#423)

## Problem

The review workflow in oz-for-oss fails to actually request team reviews when a `.github/STAKEHOLDERS` entry references a GitHub team (e.g. `@warpdotdev/oss-maintainers`). The bot's progress comment claims the review was requested, but the GitHub API call silently fails because:

1. Team slugs (containing `/`) are passed to the `reviewers` parameter, which only accepts individual user logins. Teams must go through `team_reviewers`.
2. The `GithubException` is caught and logged, but the progress comment is updated unconditionally — always claiming success.

Observed on [warpdotdev/warp#9691](warpdotdev/warp#9691 (comment)).

## Changes

**`core/workflows/review_pr.py`**
- Add `_is_team_slug()` — detects `org/team` format (presence of `/`)
- Add `_team_slug_only()` — strips the `org/` prefix for the GitHub API
- Add `_split_reviewers()` — partitions a reviewer list into `(user_logins, team_slugs)`
- Update `apply_review_result` to:
  - Split recommended reviewers into users and teams
  - Pass them to the correct API parameters (`reviewers` vs `team_reviewers`)
  - Only report successfully requested reviewers in the progress comment

**`tests/test_review_pr_reviewer_sampling.py`**
- 12 new tests: team slug detection, slug stripping, reviewer splitting, API routing for team vs user, progress comment accuracy on success and on API failure

## Testing

All 328 tests pass (including 12 new ones).

---

_Conversation: https://staging.warp.dev/conversation/ef40de82-ea29-4fa3-aeab-b5ec896017d9_
_Run: https://oz.staging.warp.dev/runs/019de41d-84ed-77b8-930a-88afee1cc598_

_This PR was generated with [Oz](https://warp.dev/oz)._
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants