eclipse-score / eclipse-score/docs-as-code

feat: asil checks

Open
#760 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
10
Forks
32
Avg merge
23h 52m
Merged PRs (30d)
52

Description

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.

Contributor guide

No contributing guide indexed for this repository

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.