Below you will find pages that utilize the taxonomy term “Immanuwell”
July 24, 2026
droast — Dockerfile linter
Version updated for https://github.com/immanuwell/dockerfile-roast to version 1.4.10.
This action is used across all versions by 0 repositories. Action Type This is a Composite action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary droast is an opinionated Dockerfile linter that catches bad practices and reports them in a blunt manner. It supports various features such as parsing heredocs, handling parser directives, shell forms, BuildKit flags, Windows paths, and PowerShell, and provides real-time feedback with inline squiggles in VS Code and lint-on-save for Neovim users.
July 19, 2026
droast — Dockerfile linter
Version updated for https://github.com/immanuwell/dockerfile-roast to version 1.4.4.
This action is used across all versions by 0 repositories. Action Type This is a Composite action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary Summary of the droast GitHub Action
The droast GitHub Action is a lint tool that checks Dockerfiles for best practices and potential issues, providing real-time feedback to developers during development. It can catch malformed syntax and catches bad practices in the Dockerfile, offering clear messages about these problems. The action works by analyzing the Dockerfile using a parser that understands various aspects of Dockerfiles, including heredocs, shell forms, Windows paths, and PowerShell.
July 18, 2026
droast — Dockerfile linter
Version updated for https://github.com/immanuwell/dockerfile-roast to version 1.4.2.
This action is used across all versions by 0 repositories. Action Type This is a Composite action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The GitHub Action droast-dockerfile-linter automates Dockerfile linting by identifying and reporting bad practices, providing feedback in a non-polite manner. It supports various parsing capabilities, including handling heredocs, parser directives, shell forms, BuildKit flags, Windows paths, PowerShell, and custom ignore files to ensure accurate detection of issues.