Provide Better Feedback That Things Are Happening
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The current design has two background tasks:
* [cargo-vet-check-submit-failure](https://github.com/axodotdev/cargo-vet-school/blob/main/.github/workflows/cargo-vet-check-submit-failure.yml) task responds to cargo-vet-check failing, unpacks the zip, POSTS to the webapp, and posts a comment
* [cargo-vet-certify](https://github.com/axodotdev/cargo-vet-school/blob/main/.github/workflows/cargo-vet-certify.yml) is triggered by the webapp when you hit the "Commit" button, runs `cargo vet certify` in a loop, then commits and pushes
In both of these cases there can be Something Important And Useful Related To The PR happening and the the only way to know is to open the Actions admin panel on the repo (but not always the same repo!).
Potential improvements:
* Have the bot comment on the PR more about "I'm gonna do this"
* Have the "Commit" button in the GUI link you the workflow
* Have the "Commit" button disable and/or display status of the workflow
* Find a way to associate the tasks with the PR so they show up along with other CI tasks
* May be multiple inflight copies, can be problematic
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading .github/workflows/cargo-vet-check-submit-failure.yml and .github/workflows/cargo-vet-certify.yml, then trace how the webapp's "Commit" button triggers cargo-vet-certify. Compare the proposed feedback approaches and define one complete workflow whose progress and completion are visible from the pull request or GUI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, rust
- Domain
- ci-cd, developer-experience, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100