Something like might let you auto-configure the Git credential helper in the docker instance based on environment variables you pass to it (such as the GIT_PRIVATE_TOKEN one I saw in the snippet you shared).

This is what the Git credentials helper does. You need to configure your Git credentials in the docker container so that Git commands executed in the container can use them. CI actions that can be configured with tokens will include them in the Git commands they execute behind the scenes, but Git commands executed by arbitrary scripts and programs within the container will not know about the tokens, let alone how to use them. Now that you have Git and Git LFS installed on your development machine you can use it with your Unity projects. Private access tokens are not, in themselves, a mechanism that automatically provides authentication in Git commands performed on the command line. These token can be used with HTTPS only according to the Github docs. Private access tokens are essentially additional passwords that you can use to authenticate with your user account instead of providing your password. My understanding is that configuring the private token in your GameCI configuration allows the Github Actions themselves to use it when performing actions, but doesn't affect Git commands not executed directly by the implemented actions. environment variables passed as also not something that Unity/UPM uses or knows about. Hi docker image is passed the GIT_PRIVATE_TOKEN environment variable, which is not a standard Git environment variable as far as I know. env BUILD_TARGET=StandaloneLinu圆4 -env BUILD_NAME=StandaloneLinu圆4 -env BUILD_PATH=build/StandaloneLinu圆4 -env BUILD_FILE=StandaloneLinu圆4 -env VERSION=0.0.124 -env ANDROID_VERSION_CODE=124 -env GITHUB_REF=refs/heads/WIP-CI-SmokeTest -env GITHUB_SHA=3c5fa83f784b6fd0c3c8538748a1942b5295c819 -env GITHUB_REPOSITORY=vr-bits/UnitySensei -env GITHUB_ACTOR=RobTranquillo -env GITHUB_WORKFLOW=SmokeTest Unity 2019 LTS -env GITHUB_EVENT_NAME=workflow_dispatch -env GITHUB_WORKSPACE=/github/workspace -env GITHUB_ACTION=_game-ci_unity-builder -env GITHUB_EVENT_PATH=/home/runner/work/_temp/_github_workflow/event.json -env RUNNER_OS=Linux -env RUNNER_TOOL_CACHE=/opt/hostedtoolcache -env RUNNER_TEMP=/home/runner/work/_temp -env RUNNER_WORKSPACE=/home/runner/work/UnitySensei -env UNITY_SERIAL -env GITHUB_WORKSPACE=/github/workspace -env GIT_PRIVATE_TOKEN=*** -volume /home/runner/work/_temp/_github_home:/root:z -volume /home/runner/work/_temp/_github_workflow:/github/workflow:z -volume /home/runner/work/UnitySensei/UnitySensei:/github/workspace:z -volume /home/runner/work/_actions/game-ci/unity-builder/v2/dist/default-build-script:/UnityBuilderAction:z -volume /home/runner/work/_actions/game-ci/unity-builder/v2/dist/platforms/ubuntu/steps:/steps:z -volume /home/runner/work/_actions/game-ci/unity-builder/v2/dist/platforms/ubuntu/entrypoint.sh:/entrypoint.sh:z unityci/editor:ubuntu-2019.4.29f1-linux-il2cpp-1 /bin/bash -c /entrypoint.sh Or check out our reference server implementation./usr/bin/docker run -workdir /github/workspace -rm -env UNITY_LICENSE -env UNITY_SERIAL=XXX -env UNITY_VERSION=2019.4.29f1 -env PROJECT_PATH=. If you're interested in integrating Git LFS into another tool or product, you might want to read the To start a discussion, file an issue, or contribute to the project, head over to the repository Just commit and push to GitHub as you normally would for instance, if your current branch is named main:Ĭheck out our wiki, discussion forum, and documentation for help with any questions you might have! To do that, use the git lfs migrate(1) command, which has a range of options designed to suit various potential use cases. wav files 'dirty' and listed in the changelist (it is not the conflict btw) every time. Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. wav filterlfs difflfs mergelfs -text, when I merge other branches that has changed. You can configure additional file extensions at anytime.

In each Git repository where you want to use Git LFS, select the file types you'd like Git LFS to manage (or directly edit your. You only need to run this once per user account. Once downloaded and installed, set up Git LFS for your user account by running: Download and install the Git command line extension.

Git lfs unity