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 14:52:30 UTC
(magpie) branch contributor-growth/5-candidate-screen updated (f79218c7 -> 843a19d3)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a change to branch contributor-growth/5-candidate-screen
in repository https://gitbox.apache.org/repos/asf/magpie.git
discard f79218c7 fix(contributor-growth): candidate-screen never truncates the pool, maps roster ids, and shows capped counts as minimums
discard 2d3a27c6 feat(contributor-growth): candidate-screen report to a verified-private repo, with verified real names
discard 6ba283bb docs(chat): link the Discord adapter tracking issue
discard b8f8eb96 fix(contributor-growth): a chat profile's own claim is not an identity; collected rows count as off-GitHub signal
discard 989a15ef feat(contributor-growth): collect community signals with a separate indicator
discard 8fdf7811 fix(contributor-to-committer): off-GitHub signal is always mandatory, never auto-MET
discard 145442eb fix(contributor-growth): compute calibration floors in code; respect caps and the assessment window
discard 35702fe9 feat(contributor-growth): calibrate thresholds from past nomination decisions
discard d4734c12 fix(contributor-metrics): date every item by the contributor's own activity inside the window
discard 1162a6bc docs(contributor-growth): describe the unified substantive-review rule in the readiness template
discard 67eac98d feat(contributor-growth): count with contributor-metrics; per-area shares and issues triaged
discard e90cf854 feat(contributor-metrics): deterministic contributor counts, area shares and automated-work weighting
discard 2f25c0c6 feat(contributor-growth): small penalty for automated work that drew maintainer pushback
discard 76b54d09 docs(designs): contributor-growth calibration, community signals and candidate screening
add 4302c2f7 fix(setup): grant the vetted-ops and scratch directories as working directories (#1418)
add cd351b54 docs(designs): contributor-growth calibration, community signals and candidate screening
add adf186a1 feat(contributor-growth): small penalty for automated work that drew maintainer pushback
add dbf3d5f4 feat(contributor-metrics): deterministic contributor counts, area shares and automated-work weighting
add c157c250 feat(contributor-growth): count with contributor-metrics; per-area shares and issues triaged
add 4c951c09 docs(contributor-growth): describe the unified substantive-review rule in the readiness template
add 6fb1f983 fix(contributor-metrics): date every item by the contributor's own activity inside the window
add f47a2318 feat(contributor-growth): calibrate thresholds from past nomination decisions
add 1ba4b3f8 fix(contributor-growth): compute calibration floors in code; respect caps and the assessment window
add 10ce5cf3 fix(contributor-to-committer): off-GitHub signal is always mandatory, never auto-MET
add 3f20ffd7 feat(contributor-growth): collect community signals with a separate indicator
add a98bb02d fix(contributor-growth): a chat profile's own claim is not an identity; collected rows count as off-GitHub signal
add 90edca4e docs(chat): link the Discord adapter tracking issue
add e6500156 feat(contributor-growth): candidate-screen report to a verified-private repo, with verified real names
add 843a19d3 fix(contributor-growth): candidate-screen never truncates the pool, maps roster ids, and shows capped counts as minimums
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 (f79218c7)
\
N -- N -- N refs/heads/contributor-growth/5-candidate-screen (843a19d3)
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:
docs/setup/sandbox-troubleshooting.md | 67 ++++++++++++++++++
docs/setup/secure-agent-setup.md | 81 +++++++++++++++++++++-
.../skills/isolated-setup-doctor/SKILL.md | 32 ++++++++-
.../scripts/probe-9-working-dirs.sh | 57 +++++++++++++++
.../skills/isolated-setup-install/SKILL.md | 27 +++++++-
.../skills/isolated-setup-update/SKILL.md | 8 ++-
.../skills/isolated-setup-verify/SKILL.md | 10 ++-
.../setup/setup_preflight/isolated_fingerprint.py | 2 +-
tools/agent-isolation/sandbox-add-project-root.sh | 45 ++++++++++--
.../tests/test_sandbox_add_project_root.py | 50 +++++++++++++
tools/skill-evals/README.md | 4 +-
.../evals/setup-isolated-setup-doctor/README.md | 4 +-
.../expected.json | 2 +-
.../report.md | 6 +-
.../interpret-probes/fixtures/output-spec.md | 3 +
.../evals/setup-isolated-setup-verify/README.md | 4 +-
.../case-10-working-dirs-missing/expected.json | 15 ++++
.../case-10-working-dirs-missing/report.md | 63 +++++++++++++++++
.../step-1-classify/fixtures/output-spec.md | 4 +-
19 files changed, 456 insertions(+), 28 deletions(-)
create mode 100755 plugins/magpie-setup/skills/isolated-setup-doctor/scripts/probe-9-working-dirs.sh
copy tools/skill-evals/evals/setup-isolated-setup-doctor/interpret-probes/fixtures/{case-17-git-hooks-unreadable => case-18-working-dirs-glob}/expected.json (70%)
copy tools/skill-evals/evals/setup-isolated-setup-doctor/interpret-probes/fixtures/{case-16-dev-tools-not-granted => case-18-working-dirs-glob}/report.md (58%)
create mode 100644 tools/skill-evals/evals/setup-isolated-setup-verify/step-1-classify/fixtures/case-10-working-dirs-missing/expected.json
create mode 100644 tools/skill-evals/evals/setup-isolated-setup-verify/step-1-classify/fixtures/case-10-working-dirs-missing/report.md