But found no issue with:
Revert to use PortableGit-2.37.3-64-bit for svn to git migration
Version: GitLab Community Edition 12.10.14
Full backup failed with command: gitlab-rake gitlab:backup:create
Version: GitLab Community Edition 12.10.14
Full backup successful with command: gitlab-backup create
GitLab Community Edition 10.1.0 5a695c4
Users created some wiki pages with title of below:
git clone ssh://git@test.gitlab.yourcompany.local:2202/com/yourcompany/general.wiki.git
- Replaced ":" character with "-" at WIKI Page Title
Special characters been identified causing cloning wiki issue:
Googled: download m3u8
https://chrome.google.com/webstore/detail/m3u8-online-video-extract/fcpefnjbneopahdnhdhahbhoccipdmdm
Convert ts files to mp4
ffmpeg -i ts_file_path -acodec copy -vcodec copy -f mp4 path+name.mp4
Projects from:
https://github.com/Momo707577045/m3u8-downloader
Thank you for sharing that
Differents:
Bare Repository won't be available in the list of Repository during Share Project below:
Public: Eclipse Git - Create as bare repository
Create as bare repository
Created Folder structure:
Git version:
PortableGit-2.28.0-64-bit.7z
Case:
Did a Git Stash in Visual Studio Code, before commit i did git pull, then my changes and new files all gone.
Read article saying that git stash won't "add" new files(untracked)
https://www.cnblogs.com/zndxall/archive/2018/09/04/9586088.html
But luckily still able get back all files(changes + new/untracked files) by git stash pop.
refs/heads/master is a branch in your working copy named master. Frequently that is a tracking branch of refs/remotes/origin/master because origin is the default name for the remote created by git clone and its primary branch is usually also named master.git rev-list refs/heads/master..refs/remotes/origin/master which will be empty if they are the same and will otherwise list the commits between them.refs/heads/ are branches that, when you have one checked out, you can advance by creating new commits. Those under refs/remotes/, however, are so-called "remote-tracking branches" - these refs just point to the commit that a remote repository was at the last time you did a git fetch <name-of-remote>, or a successful git push to the corresponding branch in that remote repository. (I wrote a blog post that talks about this difference at some length here.)