As for files that would make sense to incorporate as part of the templating, I started to collect a small list (could be transformed to a task list in an issue of the new repository):
.github/SECURITY.md.github/support.md.github/contributing.md.github/release-drafter.yml.github/renovate.json5.github/codecov.yml (not 100% sure since there are quite some special cases here across repos. the core is still the same).github/pull_request_template.md.github/ISSUE_TEMPLATE/bug-report.yml.github/ISSUE_TEMPLATE/feature-request.yml.github/workflows/ci.yml.github/workflows/cd.yml.github/workflows/release-drafter.yml.github/workflows/upstream.yml.github/workflows/update-mqt-core.ymldocs/_static/custom.cssdocs/_templates/page.htmldocs/development_guide.md (will take a bit of effort to properly template)docs/installation.md (not 100% sure, but could be nice)docs/lit_header.bib.clang-format.clang-tidy.cmake-format.yaml.git_archival.txt.gitignore (huge overlap between all repos).license-tools-config.json.pre-commit-config.yaml (not 100% straightforward to template because of, e.g., mypy dependencies)README.md (don't know if there is too much value here. certain sections and the overall structure should be the same across all repositories)noxfile.py (differs for pure-Python and C++-Python projects)ruff.toml (if we should decide to add that in favor of keeping the config in pyproject.toml to make it easier to template)uv.toml (same as ruff.toml)- (further ideas. mypy config, codecov config, ...)
Originally posted by @burgholzer in munich-quantum-toolkit/.github#44 (review)
Originally posted by @burgholzer in munich-quantum-toolkit/.github#44 (review)