ash-project/ash

Duplicate extension migrations when using multiple repos

Closed

#2,278 opened on Aug 18, 2025

View on GitHubContributor guide
 (7 comments) (0 reactions) (0 assignees)Elixir (389 forks)batch import
buggood first issue

Repository metrics

Stars
 (2,412 stars)
PR merge metrics
 (Avg merge 6d 6h) (26 merged PRs in 30d)

Description

Current Behavior

When adding a new extension with igniter that requires a migration the tool generate the migration for each repo defined in the project causing a migration error

Reproduction

https://github.com/wildcant/multi-repo-extension-duped-migration

Expected Behavior

Quoting Zach: "we probably want some kind of migrate_extensions? false callback on the repo"

Contributor guide

Research direction
The issue describes duplicate migration generation when using multiple repos with extensions. The reproduction repo is at https://github.com/wildcant/multi repo extension duped migration. The expected behavior includes a callback `migrate extensions? false` on the repo. Investigate the migration generation code in the Ash igniter tool, likely in files related to extension handling and repo configuration. Look for where migrations are generated per repo and how to conditionally skip extensions.
Tech stack
elixir
Domain
backenddatabase
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
ElixirAsh framework basicsDatabase migrations concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35