bazel-contrib / bazel-contrib/rules_distroless

FR: Detect manifest changes and automatically run lock

Open
#130 1 comment 1 reaction 0 assignees View on GitHub
feature request good first issue help wanted
Dominant language
Starlark
Stars
101
Forks
74
Avg merge
9h 42m
Merged PRs (30d)
2

Description

Currently, the lock generation is manual, and sometimes forgotten after manifest changes, it would be nice to detect manifest changes. and trigger lock generation and update the lockfile in place.

Contributor guide

Open the contributing guide

Research direction

Start by locating the manifest, lock-generation process, and lockfile handling in the repository. Determine how manifest changes can trigger lock generation and how the lockfile should be updated in place; done means those changes no longer require a manual lock-generation step.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.