cli: REPOWISE_FULL_RESCORE_INTERVAL_DAYS warning fires per repo in workspace/watch updates

Open
#1,371 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
cli, tooling

Research direction

Start by tracing the configuration-warning fix from PR fix/852-config-warnings through workspace fan-out, repowise watch, and post-commit hook updates. Reproduce an invalid REPOWISE_FULL_RESCORE_INTERVAL_DAYS in each context and verify that the warning appears once per invocation rather than once per repository.

Written by the indexing model from the issue text.

Description

Residual from the #852 config-warning fix (PR fix/852-config-warnings). An invalid REPOWISE_FULL_RESCORE_INTERVAL_DAYS prints a warning per repo per trigger in workspace fan-out, repowise watch and post-commit hook updates (KTD3's once-per-invocation intent is violated by the workspace loop).

Dominant language
Python
Stars
6.7k
Forks
711
Avg merge
1d 13h
Merged PRs (30d)
439

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from repowise-dev/repowise

All issues in repowise-dev/repowise

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.