Skip to content

chore: update issue templates and workflows for improved labeling and formatting#4501

Merged
whysosaket merged 1 commit intomainfrom
stale-bot
Mar 23, 2026
Merged

chore: update issue templates and workflows for improved labeling and formatting#4501
whysosaket merged 1 commit intomainfrom
stale-bot

Conversation

@kartik-mem0
Copy link
Copy Markdown
Contributor

Linked Issue

Closes #

Description

Overhaul GitHub issue templates, add stale bot, and add auto-labeling for issue triage.

Issue templates (O21):

  • Rewrote all 4 issue templates as .yml forms with cal.com-style pre-filled markdown (value:) so users see one dropdown + one editable text box
  • Bug Report: component dropdown + pre-filled sections (summary, repro steps, expected/actual, environment) + auto-label bug
  • Feature Request: component dropdown + pre-filled sections (use case, proposed solution, alternatives) + auto-label enhancement
  • Benchmark Submission: pre-filled sections (model, config, dataset, results table, environment) + auto-label benchmark
  • Documentation Issue: pre-filled sections (page link, issue, suggested fix) + auto-label documentation
  • Updated config.yml contact links from Embedchain to Mem0

Stale bot (O24):

  • Runs daily at midnight UTC via GitHub Actions
  • Marks issues with no activity for 90 days as stale, auto-closes after 14 more days
  • Marks PRs as stale but never auto-closes them
  • Exempts P0-critical, P1-high, good first issue, security labels
  • Processes 100 issues per run to stay within API limits

Auto-labeler:

  • When someone files an issue and picks a component from the dropdown (e.g., "Ollama"), the ollama label is auto-applied via advanced-issue-labeler
  • Maps all 9 component dropdown options to matching GitHub labels
  • Zero manual triage needed for component labels

Type of Change

  • New feature (non-breaking change that adds functionality)

Breaking Changes

N/A

Test Coverage

  • No tests needed (explain why)

GitHub Actions workflows and issue templates — tested by verifying YAML syntax and confirming label mappings match existing repo labels.

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have added tests that prove my fix/feature works
  • New and existing tests pass locally
  • I have updated documentation if needed

───────────────────────────────────────────────────────────────

@whysosaket whysosaket merged commit 65156d5 into main Mar 23, 2026
2 checks passed
@whysosaket whysosaket deleted the stale-bot branch March 23, 2026 11:04
jamebobob pushed a commit to jamebobob/mem0-vigil-recall that referenced this pull request Mar 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants