Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Show workflows across repos sorted by trigger date

Open
#528 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, typescript, vscode
Domain
ci-cd, devtools

Research direction

The issue identifies the existing Workflows section but names no files, tests, or entry points. Start by tracing how that view loads and displays one repository's workflows, then determine the scope of cross-repository data and ordering. Done means a combined view can show workflows from related repositories sorted by trigger date; the optional trigger relationship visualization needs separate scope.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe.
I have a few repos that work together, common in micro services or backend / frontend / etc decoupling. I push often with continuous delivery. Right now you can only fit a single repo's workflows on screen in the workflows section at a time. There is no tool that simply shows all of your workflow builds in a master dashboard.

Describe the solution you'd like

  • I would love to see a combined Workflows view that shows all builds for all repos in a single list, in the order that they were triggered.
  • Optionally, some repo workflows trigger other workflows in another repo, and it would be great to have a visual representation of that, like an arrow from the triggering to the triggered or something.

Additional context

Note In this screenshot how I have four related repos but expanding one takes up the entire screen, e.g. you can't even see the third and fourth repo. Further there is no chronological workflow ordering across repos.

Image
Dominant language
TypeScript
Stars
661
Forks
214
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/vscode-github-actions

All issues in github/vscode-github-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.