Checking precice-config.xml files for issues in the CI
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
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.
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.
- Dominant language
- C
- Stars
- 142
- Forks
- 168
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from precice/tutorials
-
good first issue
Difficulty 2/5 1-2 days Newbie friendliness 62/100
precice/tutorials#617 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
system-tests
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
system-tests
Difficulty 4/5 3-5 days Newbie friendliness 45/100
precice/tutorials#933 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
precice/tutorials#877 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Maintainers usually reply within 1 day
All issues in precice/tutorials
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dkfans/keeperfx#5415 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
void-linux/void-runit#141 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ARM-software/sysarch-acs#600 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day