sixfold-space/madtea
sixfold-space/madtea
SHA256
2
0
Fork 0
Code Issues 219 Pull requests Projects Releases 13 Packages Wiki Activity Actions 9

test: probe forge close-word and dependency behavior on throwaway forges #820

Merged
hexajon merged 3 commits from test/close-semantics-probe into main 2026-10-20 01:11:09 +00:00
Conversation 0 Commits 3 Files changed 2 +309
hexajon commented 2026-10-20 01:11:05 +00:00
Owner
Copy link

Summary

Adds a forge-tagged probe that runs against throwaway Forgejo and Gitea servers, at the baseline and latest pins. Every case passes on all four servers:

  • A close word on an issue with an open dependency: the merge succeeds and the issue stays open.
  • A close word after "not" still acts.
  • A keyword acts only on the reference right after it.
  • A close word in a comment on a PR acts at merge.
  • The forge refuses a cycle of two issues but accepts a cycle of three, through both the dependencies and the blocks endpoint.
  • An issue stays open when its last dependency closes.

Run it with: PKG=./internal/testforge/closeprobe/... ./scripts/forge-vm/run-forge-tests.sh

Related: #817

## Summary Adds a forge-tagged probe that runs against throwaway Forgejo and Gitea servers, at the baseline and latest pins. Every case passes on all four servers: - A close word on an issue with an open dependency: the merge succeeds and the issue stays open. - A close word after "not" still acts. - A keyword acts only on the reference right after it. - A close word in a comment on a PR acts at merge. - The forge refuses a cycle of two issues but accepts a cycle of three, through both the dependencies and the blocks endpoint. - An issue stays open when its last dependency closes. Run it with: PKG=./internal/testforge/closeprobe/... ./scripts/forge-vm/run-forge-tests.sh Related: #817
test: retry a merge the forge is still checking, and probe a three-issue ring through the blocks endpoint
Some checks failed
drift / govulncheck (pull_request) Has been skipped
Details
drift / surface-diff (pull_request) Successful in 35s
Details
drift / forgejo-smoke (pull_request) Has been skipped
Details
ci / mcp-conformance (pull_request) Successful in 1m28s
Details
ci / mcp-conformance (push) Successful in -36s
Details
drift / govulncheck (push) Has been skipped
Details
drift / surface-diff (push) Successful in -41s
Details
drift / forgejo-smoke (push) Has been skipped
Details
ci / gate (push) Failing after 3m0s
Details
ci / gate (pull_request) Failing after 9m11s
Details
bf28c63511
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
breaking
Breaking change - flag for release notes

  
bug
Something is not working

  
documentation
Documentation only

  
enhancement
New feature

  
epic
Tracking epic with dependency children

  
good first issue
Interested in contributing? Get started here.

  
help wanted
Maintainer would welcome outside help

  
refactoring
Code restructuring without behavior changes

  
resolution/duplicate
Closed as duplicate of another issue

  
resolution/invalid
Closed as invalid or not reproducible

  
resolution/wontfix
Closed as won't fix

  
security
Security issue or hardening

  
severity/critical
Security severity: critical

  
severity/high
Security severity: high

  
severity/low
Security severity: low

  
severity/medium
Security severity: medium

  
status/abandoned
Someone started, then walked away - up for grabs

  
status/blocked
Blocked by another issue or an external dependency

  
status/needs-decision
Waiting on a maintainer decision; workable once decided

  
status/needs-info
Waiting on reporter / more information before work can start

  
status/needs-verification
Done except verification in a live interactive session

  
testing
Test suite / CI infrastructure work

  
upstream
Related to an upstream repository, already reported there

No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea!820
No description provided.