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

feat: asil checks

Offen
#760 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
10
Forks
32
Ø Merge
23 Std. 52 Min.
Gemergte PRs (30 T.)
52

Beschreibung

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.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
python
Bereich
tooling
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Aktiv
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
30/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.