elastic / elastic/ai-github-actions

[workflow-patrol] Workflow drift detected: duplicate-issue-detector missing standard setup/runtime structure

Open Beginner friendly
#2,062 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
11
Forks
16
Avg merge
22h 9m
Merged PRs (30d)
31

Description

## Findings

### 1. `gh-aw-duplicate-issue-detector.md` is missing the standard runtime setup path used by nearly all peer workflows

**Which workflow deviates**
- `.github/workflows/gh-aw-duplicate-issue-detector.md`

**Majority pattern (>=75%)**
- In `gh-aw-*.md` workflow sources, `setup-commands` exists in `workflow_call.inputs` in **53/54** files.
- `gh-aw-fragments/runtime-setup.md` is imported in **53/54** files.
- `gh-aw-fragments/network-ecosystems.md` is imported in **52/54** files.

**Examples that follow the majority pattern**
- `.github/workflows/gh-aw-bug-hunter.md` (imports + `setup-commands` + `Repo-specific setup` step at lines 7, 35, 91)
- `.github/workflows/gh-aw-issue-triage.md` (imports + `setup-commands` + `Repo-specific setup` step at lines 8, 37, 96)
- `.github/workflows/gh-aw-pr-review.md` (imports + `setup-commands` + `Repo-specific setup` step at lines 7, 38, 97)

**What is different in the outlier**
- Imports omit `runtime-setup` and `network-ecosystems`: `.github/workflows/gh-aw-duplicate-issue-detector.md:4-10`
- `workflow_call.inputs` omits `setup-commands`: `.github/workflows/gh-aw-duplicate-issue-detector.md:19-49`
- No `Repo-specific setup` step appears before workflow logic; steps begin directly with `Prescan issue index`: `.github/workflows/gh-aw-duplicate-issue-detector.md:73-74`

**Suggested fix**
- Update `.github/workflows/gh-aw-duplicate-issue-detector.md` to align with the standard workflow_call template:
1. Add `gh-aw-fragments/runtime-setup.md` and `gh-aw-fragments/network-ecosystems.md` to `imports`.
2. Add the standard `workflow_call.inputs.setup-commands` input block.
3. Add the standard conditional `Repo-specific setup` step (`if: inputs.setup-commands != ''`) before the prescan step.

## Suggested Actions

- [ ] Add `runtime-setup` and `network-ecosystems` imports to `gh-aw-duplicate-issue-detector.md`
- [ ] Add `workflow_call.inputs.setup-commands` to `gh-aw-duplicate-issue-detector.md`
- [ ] Add the conditional `Repo-specific setup` step before `Prescan issue index`

> Generated by [Internal: Workflow Patrol](https://github.com/elastic/ai-github-actions/actions/runs/34481822495) · gpt53codex · 131.7 AIC · ⌖ 3.23 AIC · ⊞ 23.5K · [◷](https://github.com/search?q=repo%3Aelastic%2Fai-github-actions+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fai-github-actions%2Fworkflow-patrol%22&type=issues)
> - [x] expires on Sep 17, 2026, 1:33 PM UTC

Contributor guide

Open the contributing guide

Research direction

Start with .github/workflows/gh-aw-duplicate-issue-detector.md and compare its imports, workflow_call.inputs, and steps with gh-aw-bug-hunter.md or gh-aw-issue-triage.md. Done means runtime-setup and network-ecosystems are imported, setup-commands is accepted, and the conditional Repo-specific setup step appears before Prescan issue index.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
90/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.