Tags down


How to force my main repo to update when a submodules is updated?

By : user2175259
Date : October 15 2020, 08:10 PM
With these it helps After two days of research and trying to find a solution and by keeping in mind that maybe using a package manager could be the best solution, I ended up with this .gitlab-ci.yml change which I applied to my submodule repo:
code :
  stage: deploy
    - cd ~
    - mkdir .ssh
    - echo SSH_KEY_TO_ACCESS_GIT > ~/.ssh/id_rsa
    - chmod 600 ~/.ssh/id_rsa
    - eval `ssh-agent -s`
    - ssh-add ~/.ssh/id_rsa
    - ssh-keyscan -t rsa YOUR.GIT.com > ~/.ssh/known_hosts
    - git config --global user.email "ci@yourhost.com"
    - git config --global user.name "CI"
    - git clone --single-branch -b develop git@git.YOUR_REPO.git
    - git submodule init
    - git submodule update
    - git fetch --all
    - git reset --hard origin/master
    - cd ..
    - git add .
    - git commit -m "Update YOUR SUBMODULE automatically to latest"
    - git push origin develop
    - master

Share : facebook icon twitter icon

How do I force the main GUI thread to update a listbox after it is updated from a different thread?

By : user2133110
Date : March 29 2020, 07:55 AM
This might help you You should eliminate FindOpenForm and add a ProgressChanged event to TaskQueue. It is absolutely not TaskQueue responsibility to make direct calls to the presentation-layer (forms or controls). It is then the form's responsibility to listen for "progress-changed" events generated by tasks, and then update itself propertly.
This will easily solve your problem, it will keep simple, follow best-practices, and eliminate timing issues, threading issues, and so on.

git grep main repo and specific submodules

By : Pete Austin
Date : March 29 2020, 07:55 AM
seems to work fine REDO: I had hacked together a bash script with that script to do the paging (mentioned at the bottom), but noticed that your example already prefixed the search path. I modified your alias a little bit and now find that this works for me:
code :
    gpx = "!f() { list=$1; shift; for r in . $list; do ( cd $r; git grep $@ | perl -pe \"s|^|$r/|\"; ); done ;}; f"
git --no-pager gpx 'foo submodules/bar' --color=always -nIE '\w+\(\w*\)' | less -R
   gpxp = "!f() { list=$1; shift; for r in . $list; do ( cd $r; git --no-pager grep --color=always $@ | perl -pe \"s|^|$r/|\"; ); done | less -R ;}; f"
git gpxp 'foo submodules/bar' -nIE '\w+\(\w*\)'
git config scm.focusGroup 'foo something/bar'
git --no-pager submodule-ext foreach -t -r -c -k git grep 'expression'
git --no-pager tsfer -c -k git grep 'expression'
git --no-pager tsferp -c -k "git grep -E '\w+\(\w*\)'"
greppage() {
    git grep -E 'some(really)?complex.*\(expression\)'
export -f greppage
git --no-pager tsfer -c -k greppage
git --no-pager sube -q foreach -t -r -c -k "echo [ \$name ]'\n'; git grep --color=always -E '\w+\(\w*\)'; echo '\n\n'" | less -R
git-greps() { git --no-pager sube -q foreach -t -r -c -k "git grep --color=always $(git rev-parse --sq-quote "$@") | perl -pe \"s|^|\$name/|\"" | less -R; }
git-greps -nIE '\w+\(\w*\)'

How can I keep my org repo updated with the main repo?

By : user2539403
Date : March 29 2020, 07:55 AM
this will help Not aware of an automatic process to handle potential merge conflicts. But by following some rules, like the one described in the gitworkflows manual you can reduce the number of potential merge conflicts.
A detailed strategy is described here, with multiple branches to track feature, hotfix and release changes. This way you can merge the changes as soon as they are ready.

Local git repo force updated from a remote git repo. (thick-client deployments)

By : Ales Heal
Date : March 29 2020, 07:55 AM
seems to work fine I'm assuming you have a good reason for using Git for this, rather than rsync.
This is how I'd do it (on the Clients):

Is it possible to force git submodules to be updated?

By : A BC
Date : March 29 2020, 07:55 AM
To fix the issue you can do We have a git repository that depends on code in other git repositories. We use submodules, the usual way, to express this relationship and ensure that the supporting code lives at a standard location within the user's directory structure. Updating the supporting code is straightforward enough: , You could try and ask your colleagues to:
Privacy Policy - Terms - Contact Us © voile276.org