As I was going through the tutorial, I discovered a bug or more like an unnecessary key which could confuse new-learners.
In lit/docs/getting-started/resources.lit There is a tutorial config that teaches about put step
the get step has trigger set true which is why this pipeline would normally trigger and run indefinitely but because it is trying to add something that it has already done in the first run, it fails with nothing to commit, working tree clean in the second run.
I don't think trigger is required here.
Reproduction steps
Create a concourse pipeline definition with above code
Describe the bug
As I was going through the tutorial, I discovered a bug or more like an unnecessary key which could confuse new-learners. In lit/docs/getting-started/resources.lit There is a tutorial config that teaches about
put step
the
get
step hastrigger
settrue
which is why this pipeline would normally trigger and run indefinitely but because it is trying to add something that it has already done in the first run, it fails withnothing to commit, working tree clean
in the second run.I don't think
trigger
is required here.Reproduction steps
Expected behavior
trigger
removed or set tofalse
Additional context
No response