Repository navigation
Conversation
tests/fixtures/task_formats holds upstream task files copied in with intel#210; CodeFactor should not report on them. Signed-off-by: Nikolay Petrov <nikolay.a.petrov@intel.com>
There was a problem hiding this comment.
🔵 Needs a closer look
The PR’s sole effect depends on unverified CodeFactor support for .codefactor.yml and exclude_paths, requiring confirmation that the fixture directory is actually excluded.
No open issues 🎉
What changed in this PR
0 new findings; nothing to fix identified.
This PR adds configuration intended to exclude vendored task-format fixtures introduced in #210 from CodeFactor analysis.
Changes:
- Adds an exclusion for
dokimi/tests/fixtures/task_formats/**. - Leaves application code, tests, and CI unchanged. Whether CodeFactor honors this configuration remains unverified.
| File | Description |
|---|---|
.codefactor.yml |
Adds the vendored-fixture exclusion pattern for CodeFactor. |
Review effort: Balanced
|
🔍 OpenCodeReview found 1 issue(s) in this PR. By severity: 1 medium
Review details
|
| # SPDX-License-Identifier: Apache-2.0 | ||
|
|
||
| # Vendored upstream task-format fixtures (#210): not our code, not reviewed here. | ||
| exclude_paths: |
There was a problem hiding this comment.
Must-fix: CodeFactor's documented exclusion mechanism is repository Settings → Ignore Files, not an exclude_paths key in .codefactor.yml. There is no repository-side consumer of this configuration either, so adding this file does not establish the intended exclusion; the fixtures can continue to be analyzed. Apply the exclusion through CodeFactor's supported setting and verify it in a subsequent analysis, or provide evidence that CodeFactor actually consumes this file before relying on it.
There was a problem hiding this comment.
Decision needed (maintainer), not changed yet. The exclude_paths key in .codefactor.yml may be inert: CodeFactor documents exclusion as Settings → Ignore Files.
Options: (a) drop the file and add dokimi/tests/fixtures/task_formats/** under Settings → Ignore Files (recommended, documented path, verifiable in the next analysis); (b) keep the file only with a CodeFactor doc or report showing it reads .codefactor.yml.
Recommendation: (a). Holding until you pick.
There was a problem hiding this comment.
Maintainer decision: option (a). Dropped .codefactor.yml in 627edc9 (no config key left).
The glob dokimi/tests/fixtures/task_formats/** goes in CodeFactor Settings → Ignore Files (maintainer action, noted in the PR body).
The PR diff is now empty; the PR body says so.
antonwolfy
left a comment
There was a problem hiding this comment.
The file is well-formed and the glob matches the vendored fixtures, but nothing shows that CodeFactor reads it. One point to settle before merge, inline.
What I ran, on a Linux review host at c3441b8:
make ci-local: 30 passed, 0 failed, 7 skipped (docker, network, semgrep and other jobs that need the PR's own runner). Changed-line coverage passes; the PR touches no Python.- The YAML parses.
dokimi/tests/fixtures/task_formats/**matches the tracked fixture files. The commit carries aSigned-off-by.
Checked, no issues
- Scope: only
.codefactor.ymlis added. No test, build or CI file changes, so the stated blast radius holds. - Repo rules: no schema, docs page, nav entry or generated artifact is involved.
| # SPDX-License-Identifier: Apache-2.0 | ||
|
|
||
| # Vendored upstream task-format fixtures (#210): not our code, not reviewed here. | ||
| exclude_paths: |
There was a problem hiding this comment.
I agree with exai-bot and Copilot here; what I add is below.
Nothing in the PR shows that CodeFactor honours exclude_paths in this file, so the exclusion may be inert.
The description says so itself: the CodeFactor docs it could read describe exclusion as repository Settings → Ignore Files, not a .codefactor.yml key. The repo has no other CodeFactor config and no check that consumes this file. dokimi/tests/fixtures/task_formats/MANIFEST.yaml:49 and :61 show these fixtures were already edited "for CodeFactor", so the tool does analyse them today. If the key is ignored, the report stays as noisy as before and the file reads as if the problem were solved. I could not check CodeFactor's behaviour from here, so this rests on the description and the docs it cites.
Suggestion: confirm on a CodeFactor run for this PR that the fixtures drop out of the report. If they do not, add the same glob under Settings → Ignore Files and drop this file, or keep it only with a comment saying the setting is what does the work.
There was a problem hiding this comment.
Same decision as the reply above (Ignore Files vs exclude_paths). Holding; no change until the maintainer picks.
There was a problem hiding this comment.
Maintainer decision: option (a). Dropped .codefactor.yml in 627edc9 (no config key left).
The glob dokimi/tests/fixtures/task_formats/** goes in CodeFactor Settings → Ignore Files (maintainer action, noted in the PR body).
The PR diff is now empty; the PR body says so.
CodeFactor documents exclusion under repository Settings -> Ignore Files, not an exclude_paths key in this file. The glob moves to that setting (maintainer action); see the PR body. Signed-off-by: Nikolay Petrov <nikolay.a.petrov@intel.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #352 +/- ##
==========================================
+ Coverage 94.06% 94.29% +0.23%
==========================================
Files 297 308 +11
Lines 38018 39322 +1304
Branches 6424 6651 +227
==========================================
+ Hits 35760 37077 +1317
+ Misses 1451 1432 -19
- Partials 807 813 +6 🚀 New features to boost your workflow:
|
|
Closing: with .codefactor.yml dropped the diff is empty. To exclude the vendored fixtures, a maintainer adds |
Summary
.codefactor.ymlis dropped. CodeFactor documents exclusion as repository Settings → Ignore Files, not anexclude_pathskey in a config file, so the file had no proven effect.Maintainer action: add this pattern under CodeFactor Settings → Ignore Files:
The paths are the vendored upstream task-format fixtures from #210 (90 files), not our code.
Evidence
627edc9b; the change is the removal of the file in that commit.dokimi/tests/fixtures/task_formats/.Merge Danger
Door: two-way. Nothing to revert.
Blast Radius: CodeFactor report only. No effect on tests, build or CI.
🤖 Generated with Claude Code