Yicong-Huang opened a new pull request, #6080: URL: https://github.com/apache/texera/pull/6080
### What changes were proposed in this PR? Step 1 of the Codecov carryforward reset (see the linked issue). Codecov has drifted from `codecov.yml`: - Renamed flags (`python` → `pyamber`, `scala` → `amber`) still live in Codecov's carryforward chain, so the stale `python` flag is carried forward from a pre-rename commit and shows up in **every** PR comment (e.g. apache/texera#6048). - The `codecov.yml` header comment claimed the repo uploads four flags (`frontend`, `scala`, `pyamber`, `agent-service`); CI actually uploads **11**: `frontend`, `amber`, `amber-integration`, `pyamber`, `agent-service`, and the six platform services. This PR removes `flag_management.default_rules.carryforward` so the next full `main` build rebaselines Codecov against the current flag set, flushing the stale names out of the chain. It also rewrites the drifted header comment to list the real flag inventory. **This is intentionally temporary.** A follow-up PR restores `carryforward: true` once `main` has a clean full-build baseline. During the window, single-stack PRs may show non-run flags as `?` — expected, and the reason carryforward exists. Ordered operational steps (per Codecov's [reset guidance](https://community.codecov.com/t/remove-old-carryforward-flag/3428)): 1. Merge this PR. 2. Let a full build run on `main` (all 11 flags upload; no `python`). 3. Merge the follow-up PR re-enabling carryforward. 4. Rebase open PRs onto the new `main`. ### Any related issues, documentation, discussions? Closes #6079 ### How was this PR tested? Config-only change. Validated `codecov.yml` parses as valid YAML (`yaml.safe_load`) and that the top-level keys are now `ignore`, `coverage`, `comment` (the `flag_management` block is removed as intended). No behavior to unit-test; effect is verifiable on `main` post-merge by confirming the `python` flag no longer appears in subsequent PR comments. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Opus 4.8 (1M context) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
