Skip to content

chore: add CODEOWNERS and dependabot.yml for fork configuration#10

Open
Fearvox wants to merge 7 commits into
mainfrom
sleep-iter-5-codeowners
Open

chore: add CODEOWNERS and dependabot.yml for fork configuration#10
Fearvox wants to merge 7 commits into
mainfrom
sleep-iter-5-codeowners

Conversation

@Fearvox
Copy link
Copy Markdown
Owner

@Fearvox Fearvox commented May 13, 2026

Summary

  • Added .github/CODEOWNERS — maps fork-owned paths (4 workflows, 2 templates, 4 docs, planning/) to @Fearvox. Upstream paths intentionally unlisted.
  • Added .github/dependabot.yml — configures 6 update streams:
    • pip: EverCore, HyperMem, EverMemBench, EvoAgentBench (weekly, Monday 09:00 CST)
    • npm: game-of-throne-demo, claude-code-plugin (weekly, Monday 09:00 CST, grouped)

Test plan

  • CODEOWNERS syntax valid (22 lines, single-owner per path)
  • dependabot.yml covers all 6 dependency directories found via find
  • Labels align with existing repo labels (dependencies, python:uv, javascript)

🤖 Generated with Claude Code

Fearvox and others added 7 commits May 13, 2026 01:25
…lack mirror sync

Adds two issue templates under .github/ISSUE_TEMPLATE/ for long-lived,
auditable mirrors of in-flight upstream PRs:

- pr_tracker.yml: general PR mirror (scope, evidence, decision log, closure)
- security_tracker.yml: high-priority variant (CWE, severity, reachability,
  verification, disclosure hygiene)

Both carry a `pr-mirror` label so the Linear evermind-dash project and the
Slack #bots channel can subscribe by label. Bilingual EN + 中文.
…tream

Runs every 6 hours via cron + manual workflow_dispatch.
- Rebases fork main onto upstream/main (preserves fork-only commits like
  the issue templates)
- Force-pushes with --force-with-lease for safety
- Opens a tracking issue on conflict instead of failing silently

Uses default GITHUB_TOKEN — no PAT needed since we only push to fork.
Triggers on issues.opened and issues.labeled. When pr-mirror label is
present, creates a corresponding Linear issue in the EverMind-Dash
project via Linear GraphQL API. Comments back on GitHub with the
EVE-id link.

Idempotency: skips if a '🔗 Linear:' marker comment already exists.
Priority: 'urgent' label -> Linear urgent (1); otherwise medium (3).
On API failure: applies 'sync-failed' label for triage.

Requires (configured separately):
  Secret:   LINEAR_API_KEY    (Linear Personal API key, lin_api_*)
  Vars:     LINEAR_TEAM_ID    (EverMind team UUID)
            LINEAR_PROJECT_ID (EverMind-Dash project UUID)
…nnel

Update the disclosure-hygiene checkbox to reference #p-evermind-dash
(the actual Slack channel linked to the EverMind-Dash Linear project)
instead of the placeholder #bots.
…ents

Two compounding fixes to avoid creating multiple Linear issues from a
single GitHub issue creation:

1. concurrency group keyed on issue.number with cancel-in-progress=false
   serializes runs per issue. Second run will see the first run's
   comment and skip via existing idempotency check.

2. Tighten 'labeled' event filter to only fire when the added label is
   pr-mirror itself, not any other label. Eliminates the four extra
   runs that gh issue create --label A --label B ... triggers (one
   issues.opened + four issues.labeled = 5 events for a 4-label create).

Reproduction: gh issue create with 4 labels including pr-mirror was
firing the workflow 5 times concurrently. Idempotency check has a
~5s race window before the first run posts its bot comment, so 2-3
runs created duplicate Linear issues before the rest skipped.

Verified via Issue #4 sync producing both EVE-3 and EVE-4.
Adds the fork overnight patrol workflow, Linear-aware tracking issue creation, and docs guard support for coming-soon use-case placeholders. Verified with local script checks and passing Docs CI.
CODEOWNERS maps fork-owned paths (workflows, templates, community docs,
planning/, CLAUDE.md) to @Fearvox. dependabot.yml configures 6 update
streams: pip (EverCore, HyperMem, EverMemBench, EvoAgentBench) and npm
(game-of-throne-demo, claude-code-plugin), all weekly on Mondays at
Asia/Shanghai 09:00.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@Fearvox Fearvox added pr-mirror Long-lived mirror of an upstream PR for Linear/Slack tracking tracking Issue tracks a long-lived workflow labels May 13, 2026
@Fearvox Fearvox marked this pull request as ready for review May 20, 2026 13:16
Copilot AI review requested due to automatic review settings May 20, 2026 13:16
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

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

Labels

pr-mirror Long-lived mirror of an upstream PR for Linear/Slack tracking tracking Issue tracks a long-lived workflow

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants