-
-
Notifications
You must be signed in to change notification settings - Fork 447
Show workflow names if there are multiple configs #2978
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was a UX dessision to not show it in single workflow mode ... as in 90% of cases it will just show "woodpecker"
through @Tchoupinax thanks for submitting a pull request anyway :) An idea to address your problem, what about a mouse hover over wicht will show a info text with the name in it? |
@zc-devs Thank for the architecture schema, nice to understand!
Yes I see the problem... but basically is it not an invitation to correctly name your yaml file? The "mouse over" solution is not ideal but can work if I really want to know which workflow is running |
No, because if you have only one workflow, it should be called |
I can't find the original PR again, which has changed this behavior. What happens if a user has 5 workflows, but on PR's 4 are filtered out by a condition and only one workflow remains? Will this also not show the name of the single remaining workflow? |
Good point, that should probably show the name. It does not atm |
A fix should be simple, instead of count workflows, count reported config files |
Or just always show the name and call it |
Maybe hide only if the name is |
I love the idea! So great! |
I don't think that's a good idea as you can change the default file name and you wouldn't have any benefit from showing it. I like @6543 's approach to just count workflow configs instead of workflows. |
The problem is that you can have 3 pipelines with different conditions with the same step names and by opening the workflow there might be only one and you won't be able to tell which is executed as the name is hidden. Anyway we know what the default one is, so let's hide only the default not by count as this has a problem as I gave example above as I myself have got into this problem as I have such pipelines and have sometimes recheck what where conditions to understand which one is failing |
The approach was to count config files not workflows and I still think that's the best approach. |
@Tchoupinax could you fix the conflicts and update acording to the discussion |
I've applied the requested changes, but haven't tested it yet. |
|
||
const singleConfig = ref(false); | ||
const pipelineConfigs = ref<PipelineConfig[]>(); | ||
async function loadPipelineConfig() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we call this multiple times, I don't like it.
Either:
- Add a new field
config_count
to the repo api model - use
inject
to reuse the configs that are loaded already
-> #3767 |
Hey!
I noticed that when there is only one triggered pipeline, the name of the pipeline is not displayed. However, the information is valuable.
This MR tries to display it when there is only one pipeline