Better troubleshooting: show release workflow input values in the run summary
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 49.3k
- Forks
- 6.8k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 653
Description
Example from `.github/workflows/e2e-stress-test-flake-fix.yml`
https://github.com/metabase/metabase/blob/deac5cbcc7e68d20f7ffe71d021dafa73e6e9de6/.github/workflows/e2e-stress-test-flake-fix.yml#L34-L49
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
Start with .github/workflows/e2e-stress-test-flake-fix.yml, especially lines 34-49, to understand the workflow inputs and how the run is currently presented. Trace the release workflow configuration and verify that a completed run summary displays the supplied input values so they can be used for troubleshooting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100