#20 Update strategy

Aberto
3 anos atrás foi aberto por jcolomb · 0 comentários

A simple solution:

  • add a .tonic submodule in tonic template repo, content will always link to one specific repo (no copy)
  • add the scripts in that submodule
  • in the template add a sync script that would call that one:

    #!/usr/bin/env bash
    #
    # Upload changes from inside repository using GIN CLI
    # Works with submodules.
    # Assumes gin init was performed or the repository was downloaded via gin get
    
    
    
    
    
    
    
    loc=$(dirname $0)
    projectdir=$(git -C ${loc} rev-parse --show-toplevel)
    
    pushd ${loc} > /dev/null
    
    source ./.tonic/sync
    
A simple solution: - add a .tonic submodule in tonic template repo, content will always link to one specific repo (no copy) - add the scripts in that submodule - in the template add a sync script that would call that one: ``` #!/usr/bin/env bash # # Upload changes from inside repository using GIN CLI # Works with submodules. # Assumes gin init was performed or the repository was downloaded via gin get loc=$(dirname $0) projectdir=$(git -C ${loc} rev-parse --show-toplevel) pushd ${loc} > /dev/null source ./.tonic/sync ```
Faça login para participar desta conversação.
Sem milestone
Não atribuída
1 participantes
Carregando...
Cancelar
Salvar
Ainda não há conteúdo.