You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by po...@apache.org on 2026/09/27 15:37:38 UTC
(magpie) branch contributor-growth/2-metrics updated (6fb1f983 -> 9ee87675)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a change to branch contributor-growth/2-metrics
in repository https://gitbox.apache.org/repos/asf/magpie.git
omit 6fb1f983 fix(contributor-metrics): date every item by the contributor's own activity inside the window
omit 4c951c09 docs(contributor-growth): describe the unified substantive-review rule in the readiness template
omit c157c250 feat(contributor-growth): count with contributor-metrics; per-area shares and issues triaged
omit dbf3d5f4 feat(contributor-metrics): deterministic contributor counts, area shares and automated-work weighting
omit adf186a1 feat(contributor-growth): small penalty for automated work that drew maintainer pushback
omit cd351b54 docs(designs): contributor-growth calibration, community signals and candidate screening
add b9b7f0bd fix(pr-management-stats): treat the pr-triage-fold timestamp as untrusted input (#1419)
add 2cb1af49 fix(dev): make the pre-flight dedup test independent of glob order (#1428)
add 64728f48 docs(designs): contributor-growth calibration, community signals and candidate screening
add 9eb17ce7 feat(contributor-growth): small penalty for automated work that drew maintainer pushback
add 9342d44f feat(contributor-metrics): deterministic contributor counts, area shares and automated-work weighting
add 0512b639 feat(contributor-growth): count with contributor-metrics; per-area shares and issues triaged
add 9fe73f19 docs(contributor-growth): describe the unified substantive-review rule in the readiness template
add 9ee87675 fix(contributor-metrics): date every item by the contributor's own activity inside the window
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (6fb1f983)
\
N -- N -- N refs/heads/contributor-growth/2-metrics (9ee87675)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
tools/dev/tests/test_check_duplication.py | 9 +--
tools/pr-management-stats/reference.py | 19 +++++-
.../pr-management-stats/tests/test_fold_parsing.py | 73 ++++++++++++++++++++++
3 files changed, 94 insertions(+), 7 deletions(-)
create mode 100644 tools/pr-management-stats/tests/test_fold_parsing.py