Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[M5-5.1] Script de migração dos bancos do legacy (`luma_private.sqlite`, `luma_metrics.sqlite`) para o storage novo (usuários, personas, lembretes, interações, métricas)

Open
#151 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
44/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, sqlite
Domain
backend, databases

Research direction

Start by reading parent issue #150 and ZAPFORGE_PLAN.md §9, which the issue names for the acceptance criteria and overall definition of done. Then inspect the legacy databases luma_private.sqlite and luma_metrics.sqlite and identify the new storage entry points. Done means migrating users, personas, reminders, interactions, and metrics according to the parent issue's criteria.

Written by the indexing model from the issue text.

Description

area:legacy area:storage needs-adr type:feature

Bridger · #M5-5.1 · Sub-issue de #150 ([M5-5] Migração de dados) · Milestone M5 Luma + Dashboard

Tarefa

Script de migração dos bancos do legacy (luma_private.sqlite, luma_metrics.sqlite) para o storage novo (usuários, personas, lembretes, interações, métricas)

Critérios de aceite e DoD geral: ver a issue pai.

Referência: BRIDGER_PLAN.md §9 — M5 Luma + Dashboard

Multiplataforma (revisão de 2026-10-08, issue-mãe #265)

Se os IDs ganharem prefixo de plataforma, ou se o storage passar a ter escopo compartilhado ou por tenant (#278, #279), os JIDs do legacy precisam ser migrados para o formato novo. Depende dessas decisões.

Dominant language
JavaScript
Stars
26
Forks
6
Avg merge
43m
Merged PRs (30d)
137

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from murillous/LumaBot

All issues in murillous/LumaBot

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.