lint: --pull=always on local docker Lint tasks#826
Merged
Conversation
Match ProjectTemplate #284 - local Lint tasks always pull the current :latest image. CI is unaffected (ephemeral runners pull fresh each run). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the local VS Code Docker-based lint tasks to always pull the latest :latest images before running, keeping developer lint runs aligned with the current upstream linter containers while leaving CI unchanged (per the ProjectTemplate standard referenced in the PR description).
Changes:
- Add
--pull=alwaysto the Dockerruninvocations for localLint:tasks (EditorConfig, Workflows, Markdown, Spelling).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Applies the ProjectTemplate #284 standard: local docker
Lint:tasks get--pull=alwaysso they use the current:latestimage. CI unaffected.Note: the every-tier Dependabot auto-merge policy tracked in #799 is already in place on develop - the merge-bot has no
version-update:semver-majorguard (and no metadata step), and WORKFLOW.md (§169/§398/S12) + AGENTS.md already document every-tier. Closing #799 separately.