add context input to replace workdir and source inputs #365
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.
source#352This PR introduces a new
contextinput that replaces bothworkdirandsourceinputs. It resolves long-standing confusion around how bake-action determines what directory or Git reference to use when running bake.The
workdirinput was originally added in #76 to support running Bake from a subdirectory inside the GitHub workspace.Later, Git context support was added in #181 introducing a new
sourceinput. This created overlap and ambiguity between:workdir(local path inside workspace)source(Git context but can be skipped with.)This duality has consistently caused confusion for users, as highlighted in multiple issues and discussions. Users also pointed out that naming was inconsistent with
build-push-action, where the input is calledcontext.This unified
contextinput aligns withbuild-push-action. If a local dir is detected it will use it as working directory to run Bake otherwise it will use the Git context like it does forbuild-push-action.cc @ModerNews @polarathene @Clashsoft