Skip to content

chore: proposed for deletion by Snapper [score 12/16]#6

Open
jenmacc-dd wants to merge 1 commit into
DataDog:mainfrom
jenmacc-dd:snapper/propose-deletion/datadog-for-visual-studio-2026-06-16
Open

chore: proposed for deletion by Snapper [score 12/16]#6
jenmacc-dd wants to merge 1 commit into
DataDog:mainfrom
jenmacc-dd:snapper/propose-deletion/datadog-for-visual-studio-2026-06-16

Conversation

@jenmacc-dd

Copy link
Copy Markdown

🔴 Proposed for deletion: DataDog/datadog-for-visual-studio

This draft PR was opened by Snapper (GitHub repository pruner).
It adds a DELETION_PROPOSED.md marker file to signal that this repository
has been identified as a deletion candidate.

This PR will never auto-merge. Close without merging if deletion is not appropriate.


Score: 12 / 16

███████████████░░░░░ HIGH

Signal evidence

Signal Plane Result Weight
Last commit age GitHub Activity Last pushed 863 days ago +2
Open issues / PRs (context) GitHub Activity Clear
CI workflow runs (90d) GitHub Activity No workflow runs (90d) +1
Containers running (Datadog) Datadog Runtime No containers found in Datadog +3
k8s metrics (30d) Datadog Runtime All-zero series (30d) +3
Org-wide code references GitHub Code Search No org-wide references found +2
CODEOWNERS team ownership GitHub Activity No CODEOWNERS team +1

Agent rationale

HIGH (score 12) — last commit 863 days ago; no containers running in Datadog; zero k8s metrics in last 30d; no org-wide code references found; no CI runs in last 90 days.

Verify signals externally


What to do

  • Approve: merge this PR, then an org admin can archive or delete the repository via GitHub org settings
  • Reject: close this PR with a comment explaining why the repository should be kept

Generated by Snapper on 2026-06-16.

chore: proposed for deletion by Snapper [score 12/16]
@jenmacc-dd jenmacc-dd marked this pull request as ready for review June 17, 2026 14:10
@jenmacc-dd

Copy link
Copy Markdown
Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jun 17, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-06-17 14:10:30 UTC ℹ️ Start processing command /merge


2026-06-17 14:10:38 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2026-06-17 18:14:11 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant