feat: change resolve_install to public and include package data

[shenxianpeng]

Fix this line of code, to include it to support cpp-linter/clang-tools-pip#133

cpp-linter-hooks/cpp_linter_hooks/util.py

Line 20 in 8d893fa

pyproject_path = Path(__file__).parent.parent / "pyproject.toml"

Summary by CodeRabbit

• Chores
  • Updated PR workflow triggers for more reliable pull-request event handling.
  • Enhanced packaging metadata to include package data during installation.
• Refactor
  • Made the tool-install resolution API public and updated internal callers to use the public API, improving reuse and clarity.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.44%. Comparing base (8d893fa) to head (604c752).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #138   +/-   ##
=======================================
  Coverage   94.44%   94.44%           
=======================================
  Files           4        4           
  Lines         108      108           
=======================================
  Hits          102      102           
  Misses          6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[codspeed-hq]

CodSpeed Performance Report

Merging #138 will not alter performance

_{Comparing add-include-package-data (604c752) with main (8d893fa)}

Summary

✅ 60 untouched
⏩ 13 skipped¹

Footnotes

1. 13 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[coderabbitai]

Walkthrough

Renames an internal install helper to a public API and updates its callers and tests; adds package-data to pyproject.toml; and narrows GitHub Actions pull_request triggers to explicit event types.

Changes

Cohort / File(s)	Change Summary
GitHub Actions Workflow \.github/workflows/pre-commit\.yml	Adds explicit pull_request trigger types: [opened, synchronize, reopened, edited].
Packaging metadata pyproject\.toml	Sets include-package-data = true under [tool.setuptools] and adds [tool.setuptools.package-data] with cpp_linter_hooks = ["../pyproject.toml"].
Resolve-install API & callers cpp_linter_hooks/util.py, cpp_linter_hooks/clang_format.py, cpp_linter_hooks/clang_tidy.py, tests/test_util.py	Renames _resolve_install(...) → resolve_install(...) (exports now public); updates imports and all call sites and tests to use resolve_install. No other logic changes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Review should focus on API visibility change and its impact on exports and public surface.
• Check util.py docstring/typing and ensure no accidental behavioral changes when making the function public.
• Verify tests updated correctly and packaging metadata path is intended.

Possibly related PRs

• fix: simplify tool installation and invocation #113 — Modifies the same installation-related API and callers; directly related changes.
• Migration: From Clang Tools Binaries to Python Wheels #87 — Previous changes to the installation helper that this rename likely builds on or reverses.

Suggested labels

developer

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	Docstring coverage is 81.82% which is sufficient. The required threshold is 80.00%.
Title Check	✅ Passed	The PR title "fix: change resolve_install to public and include package data" accurately captures the two primary changes in the changeset: the renaming of the _resolve_install function to the public resolve_install function across multiple files and the addition of include-package-data = true to the pyproject.toml configuration. The title is concise, uses specific and clear language, and directly relates to the actual file modifications without being vague or misleading. Both changes are interconnected as packaging/distribution improvements and are appropriately represented in the title without excessive detail.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch add-include-package-data

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[shenxianpeng]

@coderabbitai generate docstrings

[coderabbitai]

✅ Actions performed

Initiated docstring generation; will generate only if new commits exist.

[coderabbitai]

Note

Docstrings generation - SUCCESS
Generated docstrings for this pull request at #139