Update: update CI and unsafe pointer

[vcaesar]

Please provide Issues links to:

• Issues: #

Provide test code:

Description

...

Summary by CodeRabbit

• Chores

  • Updated build toolchain to a newer version.

• Refactor

  • Improved internal image capture handling.

[gemini-code-assist]

Important

Installation incomplete: to start using Gemini Code Assist, please ask the organization owner(s) to visit the Gemini Code Assist Admin Console and sign the Terms of Services.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the Go version from 1.25.0 to 1.26.0 in the GitHub Actions workflow and modifies a nil-check condition in the CaptureImg function to use unsafe.Pointer conversion instead of direct nil comparison.

Changes

Cohort / File(s)	Summary
CI/CD Configuration .github/workflows/go.yml	Updated Go version from 1.25.0 to 1.26.0 in both the step name and go-version input.
Core Function Logic robotgo.go	Modified nil check in CaptureImg to compare unsafe.Pointer(bit) against nil instead of direct nil comparison for the C bitmap type.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

update

Poem

🐰 A hop to newer Go we go,
Version bumped from 25 to 26, don't you know!
With pointers cast in unsafe light,
Our bitmap checks are firm and tight.
No errors now, just code so right! 🎉

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is largely incomplete—it contains only template placeholders with empty or minimal content, missing issue links, test code, and a substantive description of the changes.	Complete the description by filling in the Issues link, providing relevant test code, and adding a clear explanation of what changes were made and why they are necessary.
Title check	❓ Inconclusive	The title partially relates to the changeset—it mentions 'CI' and 'unsafe pointer', which correspond to the workflow update and pointer nil-check modification, but it is vague and generic without specifically describing the main change.	Revise the title to be more specific and descriptive, such as 'Update Go version to 1.26.0 and fix unsafe pointer nil-check' to clearly communicate the key changes.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

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

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bitmap-pr

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

robotgo.go (1)

375-375: Simplify the nil-check by removing the unnecessary unsafe.Pointer conversion.

At Line 375, bit has type CBitmap, which wraps C.MMBitmapRef — a pointer type. In Go, C pointer types are directly comparable to nil, so bit == nil is clearer and more idiomatic than unsafe.Pointer(bit) == nil.

♻️ Proposed change

-	if unsafe.Pointer(bit) == nil {
+	if bit == nil {
 		return nil, errors.New("Capture image not found.")
 	}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@robotgo.go` at line 375, The nil-check uses an unnecessary unsafe.Pointer
conversion for the CBitmap value `bit`; change the condition to directly compare
the C pointer (`bit == nil`) and remove the `unsafe.Pointer` wrapping so the
check is idiomatic and simpler (update the `if unsafe.Pointer(bit) == nil {` to
directly use `bit == nil` wherever that check occurs).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@robotgo.go`:
- Line 375: The nil-check uses an unnecessary unsafe.Pointer conversion for the
CBitmap value `bit`; change the condition to directly compare the C pointer
(`bit == nil`) and remove the `unsafe.Pointer` wrapping so the check is
idiomatic and simpler (update the `if unsafe.Pointer(bit) == nil {` to directly
use `bit == nil` wherever that check occurs).

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9601698 and ff16db8.

📒 Files selected for processing (2)

• .github/workflows/go.yml
• robotgo.go