fix imports

[alessio]

Fixes #25

Summary by CodeRabbit

• New Features

  • Expanded support for Go versions, now including 1.22.x.

• Bug Fixes

  • Updated package import paths for shellescape to reflect new hosting, ensuring compatibility.

• Chores

  • Updated copyright year in relevant files to 2024.
  • Renamed Go module path for better organization and management.

[coderabbitai]

Walkthrough

The recent changes enhance the CI/CD workflow by expanding the Go version matrix in the configuration file, adding support for Go 1.22.x. Additionally, the import paths for the shellescape package have been updated across multiple files, reflecting a transition to a new hosting structure. Copyright notices have also been updated to the current year. Overall, these changes reinforce compatibility and maintain the code's reliability without altering core functionalities.

Changes

Files	Change Summary
.github/workflows/build.yaml	Expanded Go version matrix to include 1.22.x.
cmd/escargs/escargs.go, example_test.go, shellescape.go, shellescape_test.go	Updated import path for shellescape from github.com/alessio/shellescape to al.essio.dev/pkg/shellescape.
go.mod	Renamed Go module from github.com/alessio/shellescape to al.essio.dev/pkg/shellescape.
cmd/escargs/escargs.go	Updated copyright notice year from 2023 to 2024.

Poem

🐰 In the meadow where code does play,
New paths emerge, leading the way.
Go versions bloom like flowers in spring,
With shellescape's grace, let our functions sing!
Hopping along, we keep things bright,
Together we code, oh what a delight! 🌼✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 312088d and bb4dcb3.

Files selected for processing (6)

• .github/workflows/build.yaml (1 hunks)
• cmd/escargs/escargs.go (2 hunks)
• example_test.go (1 hunks)
• go.mod (1 hunks)
• shellescape.go (1 hunks)
• shellescape_test.go (1 hunks)

Files skipped from review due to trivial changes (4)

• cmd/escargs/escargs.go
• go.mod
• shellescape.go
• shellescape_test.go

Additional comments not posted (2)

.github/workflows/build.yaml (1)

13-13: LGTM! Ensure compatibility with the new Go version.

The addition of Go 1.22.x to the version matrix is a good practice to ensure compatibility with the latest Go release.

To verify the compatibility, ensure that the codebase is tested thoroughly with Go 1.22.x.

example_test.go (1)

7-7: LGTM! Verify the new import path.

The import path for the shellescape package has been updated to "al.essio.dev/pkg/shellescape". Ensure that the new path is correct and accessible.

To verify the new import path, ensure that the package is correctly resolved and accessible.

Verification successful

---

The new import path for the shellescape package is used correctly and consistently.

• The import path "al.essio.dev/pkg/shellescape" is referenced in multiple files, including shellescape_test.go, shellescape.go, and example_test.go.
• The package is being utilized correctly in various test functions and examples.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the new import path for the shellescape package.

# Test: Check if the new import path is accessible. Expect: Successful resolution of the package.
go get al.essio.dev/pkg/shellescape

Length of output: 107

---

Script:

#!/bin/bash
# Search for references to the shellescape package in the codebase
rg 'shellescape' --context 5

Length of output: 9442