microsoft / microsoft/winget-pkgs

[Package Request]: siGit Code v1.5.7

Open
#430,358 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help-Wanted Package-Request
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
616

Description

### How can we help?

I would like someone else to build the manifest.

### Please read and ensure the following

- [x] The installer meets the above requirements

### Please provide the following information

Download Page Url: https://github.com/getsigit/sigit/releases/download
Publisher: getSigit
Package Name: siGit Code
Description:
> siGit Code is a local coding agent. It runs on your machine, not someone
> else's. No API keys, no cloud round-trips, no subscription.
>
> It works two ways from the same binary. Zed and other ACP-compatible
> editors start it over stdio and talk the Agent Client Protocol to it. Run
> it from a terminal and you get an interactive chat UI instead. On Windows
> it speaks ACP; the full-screen terminal UI is Unix-only.
>
> Inference runs on-device against a GGUF model, or against siGit Code Cloud
> or any OpenAI-compatible endpoint you point it at.

Package Version: 1.5.7
Installer Url:
- https://github.com/getsigit/sigit/releases/download/v1.5.7/sigit-win-amd64.exe
- https://github.com/getsigit/sigit/releases/download/v1.5.7/sigit-win-arm64.exe

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's existing package-manifest conventions, then inspect the two provided Windows installer URLs and the package details for siGit Code v1.5.7. Done means a manifest is prepared for both amd64 and arm64 installers and is ready for repository validation.

Written by the indexing model from the issue text.

Assessment

Domain
release, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.