You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
First I would like to say that I really like the new API for pipelines.
A feature I really would like is to be able to from a workflow/job A trigger a workflow B in a different repo using the same user as in workflow A. The first is possible now, but the automatic feedback is somewhat lost since the executing user on workflow B is different than on workflow A.
Does this make sense?
The text was updated successfully, but these errors were encountered:
So you would like to trigger another pipeline from a pipeline while preserving the user?
Possible solutions I can think of right now:
we could expose a way to get the API token used in a similar way to how secrets work, or add some way of running automatically authenticated API requests, or give you a direct way of triggering another pipeline without using the API.
First I would like to say that I really like the new API for pipelines.
A feature I really would like is to be able to from a workflow/job A trigger a workflow B in a different repo using the same user as in workflow A. The first is possible now, but the automatic feedback is somewhat lost since the executing user on workflow B is different than on workflow A.
Does this make sense?
The text was updated successfully, but these errors were encountered: