eclipse-score / eclipse-score/docs-as-code
feat: asil checks
- 主要言語
- Python
- スター
- 10
- フォーク
- 32
- 平均マージ
- 23時間 52分
- マージ済み PR(30日)
- 52
説明
For PR #735 following tasks should be done:
- [ ] check process reqs (Is process correctly translated to tool requirements)
- [ ] tool reqs (Do tool requirements caputre process)
- [ ] Check metamodel graph check implementation (Does implementation mirror tool requirement)
If there is issues / gaps in the tasks above then:
- [ ] Fix gaps in implementaiton (in docs-as-code)
Finally:
- [ ] Check failures in downstream checks and create issues in the right repositories for the failures
=> As we are not maintainers in those other repositories we can not fix these issues that relate to needs in other repositories, therefore we only make an issue with the changes that will come and need to be fixed, and work with the maintainers of the repo to fix them.
If all tasks are done/ok then PR can be merged.
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
Start with PR #735 and the docs-as-code implementation. Check the process requirements, tool requirements, and metamodel graph checks against the issue’s stated expectations, then inspect downstream check failures. Done means gaps are fixed where possible and remaining cross-repository failures have issues filed with the relevant maintainers.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- python
- 領域
- tooling
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 活発
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 30/100