Replies: 2 comments 2 replies
-
Hi @borekb - thanks for the feedback. We're working on the first part now. We'll give some thought to the names in the checks UI. I've run into some length issues there myself but we've got a few other issues that we're going to look at first. Thanks again! |
Beta Was this translation helpful? Give feedback.
2 replies
-
Ref: #9050 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm trying to use reusable workflows and have two pieces of feedback:
1: I cannot reference a reusable workflow via relative path
We have a shared deployment logic that I've put into
deploy-reusable.yaml
and then we have two "real" workflows,deploy-preview.yaml
anddeploy-production.yaml
, where I'd like to do this:However, the only accepted form is
{owner}/{repo}/{path}/{filename}@{ref}
(I tried 😄) so I have to do this:deploy-reusable.yaml
deploy-preview.yaml
:deploy-production.yaml
:This double committing and inability to test changes in one go is quite annoying.
2: Name of the called workflow is shown in "checks" UI
This is mostly a cosmetic issue but the checks UI (e.g., at the end of pull requests) shows "{Workflow name} / {Job name}" so before, we had "Deploy / Preview" and "Deploy / Production".
Newly, as a side effect of the YAML refactoring, there's another part:
It feels a little bit wrong that a change of YAML structure also affects the readability of our checks UI. I think that the called workflow job name shouldn't be printed in the checks UI.
Beta Was this translation helpful? Give feedback.
All reactions