feat: add github workflows

[hoanguyenkh]

Summary by CodeRabbit

• New Features

  • Introduced automated dependency updates with Dependabot for GitHub Actions and Go modules.
  • Added workflows for linting Go code and running tests on pushes and pull requests.

• Bug Fixes

  • Enhanced error handling in the FromAntsPool function to improve robustness.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce new configuration files for automated dependency management and continuous integration in a Go project. A .github/dependabot.yml file is added to manage package updates for GitHub Actions and Go modules on a weekly basis. Two GitHub Actions workflows, golangci.yml and test.yml, are created to automate linting and testing processes, respectively. Additionally, the FromAntsPool function in pool.go is updated to include error handling during task submission, enhancing its robustness.

Changes

Files	Change Summary
.github/dependabot.yml	Introduced to configure Dependabot for automated version updates in "github-actions" and "gomod" ecosystems on a weekly schedule.
.github/workflows/golangci.yml	New workflow file added to automate linting for Go code using golangci-lint, triggered by specific events including tag pushes and branch changes.
.github/workflows/test.yml	New workflow file added to automate testing of Go code on pushes and pull requests to the main branch, executing go test with race detection.
pool.go	Modified FromAntsPool function to include error handling for task submission, now panicking on submission errors to improve robustness.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant Linter
    participant Tester
    participant Pool

    User->>GitHub: Push changes
    GitHub->>Linter: Trigger golangci workflow
    Linter->>GitHub: Lint results
    GitHub->>Tester: Trigger test workflow
    Tester->>GitHub: Test results
    User->>Pool: Submit task
    Pool-->>User: Handle submission with error check

Loading

🐰 In the garden of code, a change we sow,
With linting and testing, our project will grow.
Dependabot watches, keeping updates in line,
While errors are caught, making our code shine!
Hops of joy echo, as we code and we play,
Together we flourish, in a bright, bouncy way! 🌼

---

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.