Skip to content

feat: add PowerShell installer for Windows#295

Open
Tourniercy wants to merge 2 commits intortk-ai:developfrom
Tourniercy:feat/windows-installer
Open

feat: add PowerShell installer for Windows#295
Tourniercy wants to merge 2 commits intortk-ai:developfrom
Tourniercy:feat/windows-installer

Conversation

@Tourniercy
Copy link
Copy Markdown

@Tourniercy Tourniercy commented Mar 1, 2026

Summary

  • Add install.ps1 PowerShell installer for Windows, mirroring install.sh (arch detection, latest release download, PATH setup)
  • Update README with Windows quick install one-liner: irm .../install.ps1 | iex

Test plan

  • Run irm .../install.ps1 | iex on a clean Windows machine
  • Verify rtk.exe lands in %USERPROFILE%\.local\bin
  • Verify PATH prompt works (accept and decline)
  • Verify rtk --version after install
  • Test $env:RTK_INSTALL_DIR override

@FlorianBruniaux
Copy link
Copy Markdown
Collaborator

Hi @Tourniercy! Could you rebase on the latest master? PR #241 just merged. Your PowerShell installer PR is a good addition and we want to get it moving.

@Tourniercy
Copy link
Copy Markdown
Author

Hi @FlorianBruniaux, my branch is now updated.

@pszymkowiak
Copy link
Copy Markdown
Collaborator

LGTM — clean PowerShell installer, good error handling, arch detection, PATH setup.

Before merge:

  1. Rebase on master — README was revamped in docs: revamp README with logo, badges, and structure cleanup #371, your README changes will conflict. Adapt to the new README structure
  2. The install.ps1 script itself looks ready

Once rebased, ready to merge.

@Tourniercy
Copy link
Copy Markdown
Author

Done @pszymkowiak

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Mar 20, 2026

CLA assistant check
All committers have signed the CLA.

@Tourniercy
Copy link
Copy Markdown
Author

@FlorianBruniaux @pszymkowiak PR is ready to merge

@pszymkowiak
Copy link
Copy Markdown
Collaborator

Hi! Two things needed before we can review:

  1. Retarget to develop — this PR targets master, but all PRs should target develop. You can change the base branch in the PR settings (right sidebar).
  2. Sign the CLA — if not already done, please sign at https://cla-assistant.io/rtk-ai/rtk

Thanks!

@aeppling
Copy link
Copy Markdown
Contributor

Hey

We are cleaning up the codebase and improving the project structure for better onboarding. As part of this effort, PR #826 reorganizes src/ from a flat layout into subfolders.

No logic changes — only file moves and import path updates.

What you need to do

Rebase your branch on develop when receiving this comment:

git fetch origin && git rebase origin/develop

Git detects renames automatically. If you get import conflicts, update the paths:

use crate::git;        // now: use crate::cmds::git::git;
use crate::tracking;   // now: use crate::core::tracking;
use crate::config;     // now: use crate::core::config;
use crate::init;       // now: use crate::hooks::init;
use crate::gain;       // now: use crate::analytics::gain;

Need help rebasing? Tag @aeppling

@Tourniercy Tourniercy changed the base branch from master to develop April 1, 2026 09:22
@Tourniercy Tourniercy force-pushed the feat/windows-installer branch from f06cd47 to 015abe8 Compare April 6, 2026 13:00
@Tourniercy
Copy link
Copy Markdown
Author

Done @pszymkowiak @aeppling

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.

5 participants