android / android/nowinandroid
[Bug]: Automatic dependency guard update allows skipping checks
- Dominant language
- Kotlin
- Stars
- 21.8k
- Forks
- 4.6k
- Avg merge
- 19h 20m
- Merged PRs (30d)
- 2
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is there a StackOverflow question about this issue?
- [X] I have searched StackOverflow
### What happened?
The CI action to automatically update the dependency guard baseline doesn't result in CI running again for the new changes. This allows a PR to merge without passing CI, like what happened in #material
### Relevant logcat output
_No response_
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Inspect the CI action that automatically updates the dependency guard baseline and trace what happens after it changes the repository. Reproduce the update flow and verify that CI runs again on the resulting changes; done means a pull request cannot merge without passing the follow-up CI checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100