Automatic generation of github action status bars on top "Repositories" page for a site
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Instead of going to each action under the Actions bar at the top of the
page and getting a string to paste into a markdown file I would like
a toolkit or even just a toggle in the Settings page for Actions that
would put the status bars into the top repositorypage for the site.
Close to what I would want the top page to look like that now is just
a list of my repos on the site under "Repositories" can be found at
index.
I am new to actions, but I have 43 small repositories, each of which might
have five or six github action files and I do not have to have to click
through all those pages just to get a summary report for all my repos,
nor have to maintain a page like the example manually.
If I could call a toolkit from the YAML file to post the status to the
top page I think that would do it; or if there were a setting in the
Action Settings that let me flip on that being automatically generated
that would be good.
It is relatively easy for me to use a script that looks through all my
.github/workflows directories for files and then almost automatically
makes something like my example file, but I believe there are a good
number of people that would find such an option or toolkit useful.
I am relatively new to github actions, but I could find nothing built into github site other than going to each action and clicking on the label view and cutting and pasting the lines into a markdown file. If I have 43 repositories (and others have a lot more) with say seven actions apiece that is a lot of cutting and pasting to maintain a single-page view of the statuses instead of clicking through 43 repositories to check all the statuses.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. First clarify whether this belongs in actions/toolkit or GitHub's repository-page interface, and determine whether the desired output is a reusable toolkit call or an Actions setting. Done would mean an agreed scope for generating status summaries across repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100