This check was skipped view should hint how to enable debugging
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
If you have a feature request that is relevant to this repository, the runner, then please include the information below:
Describe the enhancement
Currently, it's possible to get a view like:
https://github.community/t/jobs-being-skipped-while-using-both-needs-and-if-unclear-why/18480/4
It'd be nice if that view had a little hint in the corner:
ℹ️ Enable step logging to see why in future runs
In theory that should result in something like: https://github.community/t/when-an-action-is-skipped-why-doesnt-the-log-detail-why/179322/2
Code Snippet
If applicable, add a code snippet.
Additional information
Add any other context about the feature here.
NOTE: if the feature request has been agreed upon then the assignee will create an ADR. See docs/adrs/README.md
Contributor guide
No contributing guide indexed for this repository
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
Read docs/adrs/README.md and the linked debug-logging documentation first, then inspect the runner repository to determine whether this skipped-check view is implemented here. Done means the skipped-check view includes a hint linking users to step logging, with behavior aligned to the examples in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100