docs(repo): say GitLab closes a merge request's issues 4 at a time, 5 minutes apart #537
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
amaurycoudr/chess-project!537
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude/close-autoclose-gitlab-migration-591a1b"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
GitLab's post-merge service schedules each closing issue's
CloseIssueWorkerwith a delay that grows by 5 minutes per wave (app/services/merge_requests/post_merge_service.rb). Agents read the issues still open as a broken auto-close and closed them by hand.Evidence
Before: the issues' state events, by
source_merge_request_id:After: the doc says to wait out the waves.
Merge Danger
Door: two-way
Blast Radius: docs