Hi @<1726047624538099712:profile|WorriedSwan6> , can you share the log?

Hey @<1523701087100473344:profile|SuccessfulKoala55>
The relevant log from the pipeline shows:

error: pathspec 'origin/${pipeline.branch}' did not match any file(s) known to git
Repository cloning failed: Command '['git', 'checkout', 'origin/$%7Bpipeline.branch%7D', '--force']' returned non-zero exit status 1.

and I believe this is because the params cannot be injected in such a way, not sure if this is a bug or normal behaviour.
I am able to to use it like so:

pipe.add_parameter(
     name='branch',
     description='github url',
     default='main'
) 

pipe.add_function_step(
     name='step1 - get data',
     function=Get_data,
     function_return=['data'],
     function_kwargs=dict(branch='${pipeline.branch}'),
     repo='<my repo>',
) 

. but not like so:

pipe.add_parameter(
     name='branch',
     description='github url',
     default='main'
) 

pipe.add_function_step(
     name='step1 - get data',
     function=Get_data,
     function_return=['data'],
     repo_branch='${pipeline.branch}',
     repo='>my repo>',
) 

Hi @<1726047624538099712:profile|WorriedSwan6> ! At the moment, only the function_kwargs and queue parameters accept such references. We will consider supporting them for other fields as well in the near future