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

feat: asil checks

Ouverte
#760 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Python
Étoiles
10
Forks
32
Merge moyen
23 h 52 min
PR mergées (30 j)
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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
tooling
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
Active
Clarté
À clarifier
Accessibilité débutants
30/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.