aboutcode-org / aboutcode-org/vulnerablecode

[Enhancement] Importer Badges

未關閉
#457 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
data-quality dev-env documentation
主要語言
Python
星號
702
分支
328
平均合併
3 天 8 小時
30 天內合併 PR
3

描述

Knowing when our importers are failing when they do would help us and downstream in future.
There are multiple ways I'm thinking to add this feature

1. The action at https://github.com/nexB/vulnerablecode/blob/87ffa8109e4f5dcb22b4c8d71eaf1711c82068d7/.github/workflows/upstream_test.yml is perfect in itself. We can just add a badge for the workflow and be done with that. Whenever any importer fails, we look at the logs and figure out how to proceed.
2. We change or create a similar action to one above with some changes
- The action as a whole never fails
- After running all the tests, it generates svgs for passing and failing importers and merges them in to one single svg
- The final svg is displayed at the project home
- This way we'll know exactly which importer is failing/passing directly looking at the home
3. Other suggestions ?

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。