Skip to content

Conversation

@zhzy0077
Copy link

@zhzy0077 zhzy0077 commented Feb 9, 2026

  • Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
  • I have read the Contributing Guide

Summary by CodeRabbit

  • New Features
    • Added Scoop package support for WorkTrunk CLI v0.23.1 (Windows 64-bit), enabling one-step installation and automated updates via the package manifest.

zhzy0077 and others added 2 commits February 9, 2026 11:08
- Use GitHub repo URL for checkver compatibility
- Fix license to SPDX format (MIT OR Apache-2.0)
- Remove wt.exe binary (conflicts with existing tool)
- Add hash regex for autoupdate

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@coderabbitai
Copy link

coderabbitai bot commented Feb 9, 2026

Walkthrough

Adds a new Scoop manifest at bucket/worktrunk.json defining a Windows x86_64 release for WorkTrunk with version, homepage, license, architecture-specific download URL and SHA256, executable name (git-wt.exe), checkver, and autoupdate rules including regex-based hash retrieval.

Changes

Cohort / File(s) Summary
Scoop Package Manifest
bucket/worktrunk.json
Add new Scoop-style manifest for WorkTrunk (Windows 64-bit): version, description, homepage, license, arch-specific download URL and SHA256, binary name (git-wt.exe), checkver, and autoupdate with version interpolation and regex-based .sha256 hash extraction.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

review-needed

Suggested reviewers

  • aliesbelik

Poem

🐰 A tiny manifest, crisp and bright,
Packed with versions, hashes tight,
Windows-ready, signed just right,
A rabbit nods — release takes flight! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The description includes the required checklist items marked as completed, confirming the contributor has read guidelines and used the conventional PR title format.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title 'worktrunk: Add version 0.23.1' accurately describes the main change—adding a Scoop manifest file for WorkTrunk version 0.23.1 to the bucket.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

worktrunk

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

Check the full log for details.

@zhzy0077
Copy link
Author

zhzy0077 commented Feb 9, 2026

/verify

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

All changes look good.

Wait for review from human collaborators.

worktrunk

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

Check the full log for details.

@z-Fng z-Fng changed the title worktrunk@0.23.1: introduce worktrunk worktrunk: Add version 0.23.1 Feb 9, 2026
@z-Fng z-Fng added the package-request-needed Create a package request issue before raising PR. Check the criteria for a package to be accepted. label Feb 9, 2026
@z-Fng
Copy link
Member

z-Fng commented Feb 9, 2026

To add a new package to this bucket, please follow the standard way to create a package request issue first and link it to your PR.

When creating a package request, you can check the criteria for a package to be accepted in this bucket, which can help you determine whether your PR is likely to be approved. The information provided in the issue can also help maintainers quickly get the necessary details.

For a package to be acceptable in this bucket, it should be:

  1. Reasonably well-known and widely used. e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks *
  2. English interface (or at least English documentation) *
  3. Latest stable version *
  4. Full version (i.e. not a trial version)
  5. Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

@z-Fng
Copy link
Member

z-Fng commented Feb 9, 2026

Please consider adding this to the Main bucket instead, as it fully meets all the criteria for inclusion.

@z-Fng z-Fng closed this Feb 9, 2026
@z-Fng z-Fng reopened this Feb 9, 2026
@zhzy0077 zhzy0077 closed this Feb 10, 2026
@zhzy0077
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

package-request-needed Create a package request issue before raising PR. Check the criteria for a package to be accepted. review-needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants