| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Codecov ReportAll modified and coverable lines are covered by tests ✅ Additional details and impacted files @@ Coverage Diff @@
## main #21 +/- ##
==========================================
- Coverage 84.21% 83.71% -0.50%
==========================================
Files 5 5
Lines 304 393 +89
==========================================
+ Hits 256 329 +73
- Misses 38 54 +16
Partials 10 10 ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Interestingly, looks like we already have, so not sure why that didn't keep actions "alive"?; reference/.github/workflows/codeql-analysis.yml Lines 7 to 10 in 8c942b0 |
Sorry, something went wrong.
Sorry, something went wrong.
|
Not sure how to handle those 2 actions; I don't have access to the repo config, but it's worth checking how they're defined and if the repo-settings / branch protection needs updating (they're a big pain to set up if names change etc). |
Sorry, something went wrong.
Need tot upgrade that workflow 😅 |
Sorry, something went wrong.
|
LOL; that's what this PR does. Fun chicken-and-egg case then? |
Sorry, something went wrong.
|
I'm inclined to merge this. There is no way forward. Thoguhts? |
Sorry, something went wrong.
|
Yeah, easiest is to remove them from the "required" checks in branch protection, then after it's merged, we can probably add them back |
Sorry, something went wrong.
|
Done, let's merge |
Sorry, something went wrong.
|
SGTM; I don't have permissions though ☺️ |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
No description provided.