Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Package Request]: siGit Code v1.5.13

Open Beginner friendly
#447,900 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@paydii is already working on this.

Since Oct 4, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
yaml
Domain
release

Research direction

Read a nearby package manifest in the repository to follow its structure, then use the supplied publisher, package details, version, and Windows installer URLs to add the siGit Code manifest. Validate the manifest and confirm its installer URLs match the provided release links.

Written by the indexing model from the issue text.

Description

Needs-Triage
How can we help?

I would like someone else to build the manifest.

Please read and ensure the following
  • 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.13
Installer Url:

Dominant language
No language data
Stars
11.1k
Forks
10.2k
Avg merge
1h 31m
Merged PRs (30d)
676

Getting set up

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.

More from microsoft/winget-pkgs

All issues in microsoft/winget-pkgs

Similar issues

More Release issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.