This commit implements Phase 4 goals from the Daily Backlog Burner roadmap
by adding structured issue templates to improve issue triage and quality.
Added templates:
- Bug Report: Comprehensive template for crash/correctness issues
- Performance Issue: Specialized template for performance problems
- Feature Request: Structured template for enhancement requests
- Question: Template that guides users to appropriate channels
- Build/Installation: Template for compilation and setup issues
- Other: Catch-all template for miscellaneous issues
- Config: Directs users to external resources (Discussions, Stack Overflow)
Benefits:
- Improves issue quality through structured reporting
- Reduces maintainer time spent asking for missing information
- Guides users to appropriate channels (Discussions vs Issues)
- Enables better categorization and prioritization
- Addresses identified patterns from backlog analysis
These templates directly support the backlog management goals identified
in issue #7903, helping transform the issue process from reactive to
well-organized community engagement.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add --merge-mode-functions=separate flag to all gcovr commands
- Resolves AssertionError with C++ template destructors on multiple lines
- Fixes coverage HTML and text report generation
- Coverage reports now generate successfully without merge conflicts
This commit adds the GitHub Action configuration file for setting up
the Z3 build environment for performance development work.
The action includes:
- Installing build dependencies (cmake, ninja, python3, etc.)
- Cleaning any polluted source tree from previous Python builds
- Configuring CMake with RelWithDebInfo for performance work
- Building Z3 and test executables
- Cloning z3test repository for benchmarks
- Setting up performance measurement tools
- Creating micro-benchmark infrastructure
This configuration is based on the research and plan outlined in
issue #7872 and follows the standard CMake build process documented
in README-CMake.md.
> AI-generated content by [Daily Perf Improver](https://github.com/Z3Prover/z3/actions/runs/17735701277) may contain mistakes.
This adds the GitHub Action configuration needed to:
- Build Z3 with coverage instrumentation using clang/gcov
- Run comprehensive test suite including unit tests, regression tests, and examples
- Generate HTML coverage reports with detailed file-by-file analysis
- Upload coverage reports as artifacts for analysis
The configuration is based on the existing disabled coverage.yml workflow
and follows Z3's CMake build system with Ninja generator.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* fix: add generating META for ocamlfind.
* Patch macos. We need to keep the `@rpath` and use environment var to enable the test because we need to leave it to be fixed by package managers.
* Trigger CI.
* Debug.
* Debug.
* Debug.
* Debug.
* Debug.
* Debug.
* Hacky fix for ocaml building warning.
* Fix typo and rename variables.
* Update doc for `mk_context`.
* Migrating to cmake.
* Migrating to cmake. It builds both internal or external libz3.
* Start to work on platform-specific problem.
* Messy notes.
* debug.
* Cleanup a bit.
* Fixing shared lib extension.
* Minor.
* Resume working on this PR.
* Remove including `AddOCaml`.
* Keep `z3.ml` and `z3.mli` in the src but specify the generated file in the bin.
* Keep `ml_example.ml` in the src.
* Try github action for ocaml.
* Add workflow using matrix.
* Fix mac linking once more.
* Bypass @rpath in building sanity check.
