github →

Request

Issue #290

draft pr open
Verification
Verified — checks passed

We installed dependencies and ran lint, build, and test in a sandbox — all passed.

Could not tell if it addresses the issue (100% confidence)

An AI estimate of whether the change actually fixes the issue — the checks themselves only confirm nothing broke. It's a hint for review, not a pass/fail check.

Why?

The issue has no title or body, so there is no stated request to evaluate against; while the diff modifies `number.go` to change `strconv.ParseInt` and `strconv.ParseUint` from base 0 to base 10 and adds test cases for '08' and '-08', it is impossible to confirm this resolves a reported issue without any description of the problem.

  • lintpassed · 468ms
  • buildpassed · 86ms
  • testpassed · 220ms
    ?   	github.com/spf13/cast/internal	[no test files]
    ok  	github.com/spf13/cast	(cached)

typecheck is not defined separately in this repo.

Ran 6/9/2026, 7:52:23 PM · go:go

Get the code

Pull this branch
With gh CLI
gh pr checkout 1 --repo kamransiddiqui/cast
Raw git
git fetch https://github.com/kamransiddiqui/cast.git gitgot/issue-290
git checkout -b gitgot/issue-290 FETCH_HEAD

Fork-mode request: the branch lives on kamransiddiqui/cast (your fork), not spf13/cast, so the commands above target the fork.

Drive locally

Paste this into your local coding agent (Claude Code, Cursor, etc.) to continue iterating with full repo context.

Context prompt
You are continuing work on a draft PR for spf13/cast, addressing issue #290.

First, check out the branch with gitgot's first-pass change (run from a clone of the repo):
  gh pr checkout 1 --repo kamransiddiqui/cast

Then review the diff and:
- run the project's lint/typecheck/test commands and fix anything broken
- if the diff is wrong-headed, revert it and start fresh from the issue
- keep the change tight; do not refactor unrelated code
PR thread
  • No comments on the PR yet. Use the form below to start the thread.