Migrate CI pipeline from Travis CI to GitHub Actions

[PeterDaveHello]

Migrate the CI pipeline from Travis CI to GitHub Actions.

• README.md

  • Replace the Travis CI build status badge with a GitHub Actions build status badge.

• .github/workflows/ci.yml

  • Create a new GitHub Actions workflow file named ci.yml.
  • Add a job for shellcheck using node:18 image.
  • Add a job for Docker build using ubuntu-latest image.

• .travis.yml

  • Remove the Travis CI configuration file.

---

For more details, open the Copilot Workspace session.

Summary by CodeRabbit

• New Features

  • Introduced a new continuous integration workflow using GitHub Actions for enhanced automation.
  • Added jobs for linting Dockerfiles and building Docker images.

• Bug Fixes

  • Updated the build status badge in the README to reflect the transition from Travis CI to GitHub Actions.

• Documentation

  • Clarified Docker image repository details in the README, including links to GitHub Container Registry and Docker Hub.
  • Improved formatting and clarity of usage instructions in the README.

[coderabbitai[bot]]

📝 Walkthrough

Walkthrough

This pull request introduces a new GitHub Actions workflow configuration file (ci.yml) for continuous integration, replacing the previous Travis CI setup indicated by the deletion of the .travis.yml file. The new workflow includes two jobs: dockerfile_lint for linting Dockerfiles and docker_build for building Docker images. Additionally, the README.md file has been updated to reflect this transition, including a change in the build status badge and clarifications regarding the Docker image repository.

Changes

File	Change Summary
.github/workflows/ci.yml	New workflow file added with jobs: dockerfile_lint and docker_build for CI tasks.
.travis.yml	Deleted the Travis CI configuration file.
README.md	Updated build status badge to GitHub Actions, clarified Docker image repository details, and improved text formatting.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHubActions as GitHub Actions
    participant DockerfileLint as Dockerfile Lint
    participant DockerBuild as Docker Build

    User->>GitHubActions: Push or Pull Request to master
    GitHubActions->>DockerfileLint: Execute linting job
    DockerfileLint->>GitHubActions: Linting results
    GitHubActions->>DockerBuild: Execute build job
    DockerBuild->>GitHubActions: Build results

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[PeterDaveHello]

/review

[qodo-code-review[bot]]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Build Validation The Docker build step only builds the image but doesn't verify if it runs correctly. Consider adding a test step to run the container and validate its functionality. - name: Build Docker image run: docker build -t tor-socks-proxy:${{ github.sha }} . Cache Usage The npx cache is stored in a local directory which won't persist between workflow runs. Consider using GitHub Actions cache to speed up subsequent runs. run: npx --cache .npx dockerfile_lint