build con pacchetti in sviluppo per demo #16
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
in teoria ho messo solo workflow_dispatch come trigger, però tra le actions non vedo questa build |
mamico
reviewed
Nov 23, 2023
mamico
approved these changes
Nov 23, 2023
Non si è aggiornato il titolo, ma credo sia questa: https://github.com/RedTurtle/iocomune-backend/actions/workflows/build_demo.yml |
credo che il problema sia che se non è nel default branch, non lo aggiorna bene..per ora ho messo il trigger anche alle pr |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ho aggiunto una configurazione per avere una build che gestisca dei pacchetti in sviluppo con mx.dev.
La build principale non viene toccata, poi c'è un Dockerfile.demo che usa mx.dev che di volta in volta si può compilare con quello che si vuole e viene fatta un'immagine con il tag :nome_del_branch_demo