TARGETS
========

alreadyexist
------------
✔ The Git branch "master" already exists, nothing else to do.
✔ The git branch "master" already exist on the specified remote.

default
-------
⚠ The git branch "v1" does not exist: creating it.
⚠ The git branch "v1" has been created.
git branch "v1" has been created.

Create a pull request for 'v1' on GitHub by visiting:
     https://github.com/olblak/nocode/pull/new/v1

⚠ The git branch "v1" was pushed successfully to the specified remote.

ERROR: something went wrong in target "default" : "no changed file to commit"

Pipeline "GITBRANCH.YAML" failed
Skipping due to:
	targets stage:	"something went wrong during target execution"

=============================

REPORTS:


✗ GITBRANCH.YAML:
	Source:
		✔ [default] Get Latest committed branch (kind: gitbranch)
	Condition:
		✔ [default] Get Latest committed branch (kind: gitbranch)
		✔ [master] Get Latest committed branch (kind: gitbranch)
	Target:
		✔ [alreadyexist] Test that the branch already exist. (kind: gitbranch)
		✗ [default] Create the branch v1 if needed (kind: gitbranch)


Run Summary
===========
Pipeline(s) run:
  * Changed:	0
  * Failed:	1
  * Skipped:	0
  * Succeeded:	0
  * Total:	1
ERROR: ✗ 1 over 1 pipeline failed
ERROR: command failed
[1]    22549 exit 1     ./bin/updatecli apply --config e2e/updatecli.d/success.d/gitBranch.yaml

olblak: in the case of gittag (and gitbranch if implemented for targets) targets, would that make sense to add the .git file as the changed file?
olblak: I'm also working on removing the concept of SCM from targets (to delegate it to actions only). As part of this experiment, I thought about how the plugin should handle themselves the return status (instead of trying magically to determine it).
olblak: OH. Can you share your manifest with this error please, I think I have an idea. (TL;DR; you don't need an scmid for a target of kind gittag)