Yicong-Huang opened a new pull request, #6088: URL: https://github.com/apache/texera/pull/6088
### What changes were proposed in this PR? Step 2 (final) of the Codecov carryforward reset started in #6080. #6080 removed `flag_management.default_rules.carryforward` and let `main` rebuild once under the current flag set, flushing the stale renamed flags (`python`, `scala`, and the newly-surfaced `python-rest`, `amber-rest`) out of the carryforward chain. This PR re-enables carryforward so single-stack PRs keep backfilling non-run flags from the base report, and drops the temporary `#6079` markers. Net effect versus pre-#6080: **identical functional config** — the only lasting change from the whole exercise is the header comment, now corrected to the real 11-flag inventory (was falsely claiming four: `frontend`, `scala`, `pyamber`, `agent-service`). **⚠️ Draft / verification gate.** This PR's own Codecov comment is the A/B test for the reset: - #6080 (carryforward **off**) rendered `python` as `?` and omitted `scala` / `python-rest` / `amber-rest`. - This PR (carryforward **on**) must NOT resurrect any of those as a `0.00%` carried-forward row. Do not merge until the Codecov comment here is confirmed clean. If a stale flag reappears, it means `main`'s report still retains a `0.0` entry for it (the flags API currently shows `python`/`scala`/`python-rest`/`amber-rest` at `0.0`), and it must be deleted from the Codecov Flags page (admin) before this merges. ### Any related issues, documentation, discussions? Follows #6080. Closes #6079. ### How was this PR tested? Config-only change. Validated `codecov.yml` parses as valid YAML and that the functional blocks (`flag_management`, `coverage`, `comment`) match the pre-#6080 configuration byte-for-byte, leaving only the corrected header comment. Behavioral verification is the Codecov comment on this PR (see the verification gate above). ### 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]
