Olivier Vernin
Olivier Vernin
> thinking interesting problem. What does the ActionID maps to in the reality of a GitHub PR (or a GitLab MR)? > > Is it the source branch's name or...
> thinking interesting problem. What does the ActionID maps to in the reality of a GitHub PR (or a GitLab MR)? > > Is it the source branch's name or...
at the moment the actionID is generated based on the pipeline title and action title. But in same case those title contain dynamic information such as the latest version which...
> How does these Action ID / Pipeline ID are exposed to end user? actionID is not exposed to end user, and imho it should be avoided. The moment the...
> actionID == pipelineID + In the current design using `pipelineID` as a namespace for the `actionID` is useless, because by design, an action can only be link to one...
> must be unique in a given pipeline This is why I am wondering if having the ability to generic uniq ID per resource would allow me to solve this...
Thanks for the sharing, I wasn't aware of this and it would be a great feature
I am reopening this issue as I spotted some issues which I can't explain yet. When a pipeline has one target and so one commit, it seems to work great...
For info, I am putting the GitHub API commit behind the experimental flag for so I can release it while taking more time to do additional testing
@MattiasAng , It's great to hear you have an idea how to solve this. There are three workflows which can update the same pullrequest: * One pipeline(aka manifest) containing one...