-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Phoenix Umbrella projects #17
Comments
Yeah, there really isn't any good way to manage this with the current design of git_ops. It uses git tags to determine previous versions, and things like that. So you could maybe work it out where only one app in the umbrella is versioned with git_ops for now, but that probably wouldn't be worth it. I've been meaning to refactor git_ops to instead use like a |
Its a fair amount of work, though, and I don't really plan on doing it anytime soon. |
I might be interested in this use case for a personal project... I don't know if this would work but perhaps I'm not sure if trying to circumvent git to do multiple releases under the same repo would be a good pattern though. Using multiple repos/ submodules seems very reasonable to me if you want to do multiple releases of independent apps. But it seems that there's another question here that is more important than how to implement releases with umbrella apps: "how to semver an umbrella app"; and that depends on how you release to your end-user. It's also important to reference the docs on this subject:
|
Agreed. Overall I doubt the juice is worth the squeeze, but git submodules could definitely be a solution, along with the umbrella release task. I'd happily review a PR to that effect. |
Summary: Currently git_ops doesn't seem compatible with Phoenix umbrella projects.
Expected Behavior
Install git_ops on each one of the umbrella apps
Inside the app folder execute
mix git_ops.release --initial
Git ops should initialize the project on the right context
Current Behavior
The following error happens when executing at
Alternative
Installed at the main umbrella project resulted on a different failure where git_ops can't read the configuration from the child app.
The text was updated successfully, but these errors were encountered: