Skip to content

Conversation

@cesarcoatl
Copy link
Member

@cesarcoatl cesarcoatl commented Jun 17, 2025

pre-commit: add hadolint-coatl repo

Summary by Sourcery

Update devcontainer Dockerfile to use the requirements file in pkg and clean up temporary files, and add hadolint to the pre-commit configuration

Build:

  • Copy requirements from pkg/requirements.txt in the devcontainer Dockerfile and remove temporary files after installation

CI:

  • Add hadolint-coatl repository and enable the hadolint hook in pre-commit

pre-commit: add hadolint-coatl repo
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jun 17, 2025

Reviewer's Guide

Adjusted development container setup by updating requirement file path and cleaning temporary files in the Dockerfile, and enhanced pre-commit checks by adding a hadolint hook.

Flow diagram for pre-commit hadolint hook addition

flowchart TD
    A[pre-commit run] --> B{Check hooks}
    B -->|hadolint| C[Run hadolint on Dockerfiles]
    C --> D[Report linting results]
    B -->|other hooks| E[Run other pre-commit hooks]
Loading

File-Level Changes

Change Details Files
Updated Dockerfile to copy requirements from new location and clean up temporary files
  • Changed COPY path for requirements file to pkg/requirements.txt
  • Added removal of /tmp/* after pip install
.devcontainer/Dockerfile
Added hadolint-coatl to pre-commit hooks
  • Introduced new repository entry pointing to hadolint-coatl v2.12.1b0
  • Configured hadolint hook under the new repo
.pre-commit-config.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@cesarcoatl cesarcoatl merged commit 052331b into main Jun 17, 2025
2 checks passed
@cesarcoatl cesarcoatl deleted the chore/devcontainer/requirements branch June 17, 2025 20:17
Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @cesarcoatl - I've reviewed your changes - here's some feedback:

  • Consider splitting the path change in the Dockerfile and the addition of the hadolint hook into two separate commits or PRs to keep each change focused.
  • Instead of rm -rf /tmp/*, scope the cleanup to just the requirements file (/tmp/requirements.txt) to avoid accidentally removing other temp data.
  • Make sure any other scripts or CI configurations referencing requirements.txt are updated to use the new pkg/requirements.txt path.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Consider splitting the path change in the Dockerfile and the addition of the hadolint hook into two separate commits or PRs to keep each change focused.
- Instead of `rm -rf /tmp/*`, scope the cleanup to just the requirements file (`/tmp/requirements.txt`) to avoid accidentally removing other temp data.
- Make sure any other scripts or CI configurations referencing `requirements.txt` are updated to use the new `pkg/requirements.txt` path.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants