Checking precice-config.xml files for issues in the CI
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 142
- Forks
- 167
- Avg merge
- 20h 24m
- Merged PRs (30d)
- 11
Description
We could integrate https://github.com/precice/config-check in the CI (ideally, via the pre-commit hooks, see https://github.com/precice/precice-pre-commit-hooks)
Suggested by @uekerman.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's CI configuration and any existing pre-commit setup. Read the precice/config-check and precice/precice-pre-commit-hooks projects to determine the supported integration path, then verify that the CI checks the precice-config.xml files and fails on reported issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100