Skip to content

[Bug]: Update AL-Go Settings workflow failing, You're on a case-insensitive filesytem #2034

@nickgoddard777

Description

@nickgoddard777

AL-Go version

8.0

Describe the issue

When the Update AL-Go Settings workflow ran last night it failed with the error:
[error]Unexpected error when running action. Error Message: error: You're on a case-insensitive filesystem, and the remote you are trying to fetch from has references that only differ in casing. It is impossible to store such references with the 'files' backend. You can either accept this as-is, in which case you won't be able to store all remote references on disk. Or you can alternatively migrate your repository to use the 'reftable' backend with the following command: git refs migrate --ref-format=reftable Please keep in mind that not all implementations of Git support this new format yet. So if you use tools other than Git to access this repository it may not be an option to migrate to reftables. ExitCode: 1 Commandline: git fetch --quiet --no-tags , StackTrace: at CmdDo, D:\a_actions\microsoft\AL-Go-Actions\v8.0\Github-Helper.psm1: line 298 <- at invoke-git, D:\a_actions\microsoft\AL-Go-Actions\v8.0\Github-Helper.psm1: line 367 <- at , D:\a_actions\microsoft\AL-Go-Actions\v8.0\GetWorkflowMultiRunBranches\GetWorkflowMultiRunBranches.ps1: line 36 <- at , D:\a_temp\2f38634b-251f-48a0-92ea-2d1442706869.ps1: line 3 <- at , D:\a_actions\microsoft\AL-Go-Actions\v8.0\Invoke-AlGoAction.ps1: line 21 <- at , D:\a_temp\2f38634b-251f-48a0-92ea-2d1442706869.ps1: line 2 <- at , : line 1

It worked fine the night before and I can't see any changes that were made to the main branch yesterday, the last commit was 17th Nov.

We also have this running on 22 other repos and it worked fine on those last night so I am guessing it might be something to do with this repo but I have no idea where to start looking.

Expected behavior

The workflow should run successfully

Steps to reproduce

The Update AL-Go System Files workflow is set to run every night at midnight.

Additional context (logs, screenshots, etc.)

UpdateALGoIssueLog.txt

Metadata

Metadata

Assignees

No one assigned

    Labels

    Need more infoPlease add more info about how to repro the problemUnrelated to AL-GoThis issue is unrelated to AL-GobugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions