We can automate installation of Git and friends (and even include a "latest" option) by setting up a repository and pattern to download releases from, and then automatically running those in succession. This will improve workflow by removing the need to download separately and open from the browser, and it will give an opportunity for us to not exit on fail and rather repeat the version check/install process.

Sometimes, our rebase will fail and users will get stuck in a state where their index is at origin, but HEAD is at the previous local. This results in tons of changes and untracked files from the origin's changes.

UE4GitPlugin allows for selecting a custom git.exe, and we should too, especially since versions are enforced. Should be a matter of adding a PBSync user config, and adding a new getter for git executable name. Should also investigate Git LFS, but it is less important since that should be standard.

Aborting the repo update because of an unknown error. Request help in #tech-support to resolve it, and please do not run UpdateProject until the issue is resolved.

On branch promoted
Your branch and 'origin/promoted' refer to different commits.
(use "git status --ahead-behind" for details)

Changes not staged for commit:
(use "git add/rm ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)

Need to restore state back

PBSync can automatically set read-only for unlocked files, unlock unchanged assets, and lock changed ones, as Git LFS in conjunction with UE4 Ed can get stuck in invalid states sometimes.

When longtail fails with "Invalid JWT" we should recommend syncing time

instructions: https://partner.steamgames.com/doc/sdk/uploading#3

code:

• https://github.com/ProjectBorealis/PBSync/blob/main/pbpy/pbdispatch.py
• https://github.com/ProjectBorealis/PBSync/blob/main/pbpy/pbbutler.py
• https://github.com/ProjectBorealis/PBSync/blob/main/pbpy/pbsteamcmd.py
• https://github.com/ProjectBorealis/PBSync/blob/main/pbsync/__main__.py#L516

Git repo now configured properly for UE4Editor to detect a conflict and prompt for a resolution. However, we block launches from happening when a merge conflict is encountered. Thus, we should investigate the UE4Editor workflow for this, and confirm everything is working smoothly. It may require creating a custom mergetool for git (to replace the default p4merge.exe in UE4Editor, which isn't found in path).

Currently, we don't do a great job of syncing up a repo if it is force pushed. We should add a check for this, and safely reset the repository instead of rebasing.

Config is under Saved/Config/Windows/SourceControlSettings.ini. We can easily fill this out with the information we have.

[SourceControl.SourceControlSettings]
Provider=Git LFS 2

[GitSourceControl.GitSourceControlSettings]
BinaryPath=C:\Program Files\Git\bin\git.exe
UsingGitLfsLocking=True
LfsUserName=mastercoms

Git credential manager for windows is deprecated in favor of GCM Core. We can automatically remove the former.

Skip rebase ahead (ffdd537)

git rebase --continue
rm -rf .git/rebase...

UE4 commandlets, although very useful, can be hard to access. Providing an interface in PBSync to list them would improve productivity and UE4 project health.

Programmers may forget to regenerate project files when there is new source file content, and may not be on the latest binaries. We can fix this through UVS.

GH CLI now supports what we use Hub for: auth and release downloads. We should upgrade to GH CLI as Hub is deprecated by GitHub and is only community supported.

ue4v files are in a standard ini format which configparser can easily read instead of the manual IO loop we have now.

We can possibly use the UE Python API to trigger content reloads for new assets, instead of requiring the editor to close.

We don't handle this very gracefully. We should pop the stash, and let users resolve it in editor.