fix(ci): remove linting temp, and always build on docker changes

[tankerkiller125]

Hopefully fixes weird cache build issues and also temp removes the lint checks for the binary releases.

Summary by CodeRabbit

• Chores
  • Updated GitHub workflows to improve efficiency and accuracy of Docker and binary publishing processes.
  • Commented out sections related to backend and frontend tests in binaries publish workflow.
  • Refined file paths and caching settings in Docker publish workflows.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates streamline workflow processes by refining cache settings, specifying triggering file paths, and commenting out specific test sections. These changes enhance the efficiency and organization of Docker publishing and workflow management within the GitHub Actions environment.

Changes

Files	Change Summary
.github/workflows/binaries-publish.yaml	Commented out sections related to backend and frontend tests.
.github/workflows/docker-publish-rootless...	Added paths for triggering workflows based on file changes, and modified cache settings.
.github/workflows/docker-publish.yaml	Added and modified paths for Docker-related files and workflows, and adjusted cache directives.

In systems' veins, the workflows flow,
Adjusting paths where engines go,
With caching's breath, they find new speed,
Docker's tasks and triggers heed.
Efficiency refined, now watch it glow,
In digital realms, with grace they show. 🚀🛠️

---

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 Configration 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 91cd0d1 and 0910cc4.

Files selected for processing (3)

• .github/workflows/binaries-publish.yaml (1 hunks)
• .github/workflows/docker-publish-rootless.yaml (2 hunks)
• .github/workflows/docker-publish.yaml (2 hunks)

Files skipped from review due to trivial changes (2)

• .github/workflows/binaries-publish.yaml
• .github/workflows/docker-publish-rootless.yaml

Additional comments not posted (2)

.github/workflows/docker-publish.yaml (2)

11-14: Excellent addition of Docker-related paths to workflow triggers.

Including Dockerfile, Dockerfile.rootless, .dockerignore, and .github/workflows ensures that relevant changes trigger the workflow, enhancing its efficiency and accuracy.

Also applies to: 22-25

---

92-93: Verify the intent behind commenting out cache settings.

Commenting out the cache settings could be a temporary measure to address the cache build issues. Ensure to revisit and re-enable these settings once the issue is resolved for optimized workflow performance.