Lint tasks run in wrong workflow?

Following the example from the documentation, I created a new workflow file for linting, called lint.yml. I have another workflow file named ci.yml that handles running tests (and, previously, running yarn lint on the project). Maybe this is intended behavior, but when the “Run linters” job runs, it creates new jobs for each linter in the “CI” workflow, rather than the “Lint” workflow. Consequently, it’s a bit confusing in the UI. The “Lint” workflow is missing jobs our team thinks it should have while “CI” has jobs that it shouldn’t.

[nirvdrum]

That’s indeed the behavior I’m looking for. But what I see instead is:

Although, now that I see that it’s supposed to work the way you showed, I worked on my config a bit more and think I figured out the problem. In my CI workflow, I have a job named lint that runs tslint, as lint-action doesn’t have support for it. If I remove that job from my CI workflow, the lint-action jobs end up in in the Lint workflow. I haven’t looked much at the source, but it seems like there may be a look-up problem there.

[andrewandante]

Just to add I’m seeing this behaviour as well, it seems to attach to one of two of my other workflows, and as far as I can tell the only thing they have in common is that they have no name: parameter. I’ve added them to my workflows and that seems to have helped, but only time will tell.