[Bug]: CheckForUpdates fails with 404 when fetching latest SHA from microsoft/AL-Go-PTE template

[ChrisChristophers]

AL-Go version

8.1

Describe the issue

When running the "Update AL-Go System Files" workflow (CheckForUpdates action), the workflow
fails with a 404 error when attempting to retrieve the latest commit SHA from the template repository
https://github.com/microsoft/AL-Go-PTE@main.

The full error message is:

Unexpected error when running action. Error Message: Failed to update AL-Go System Files.
Could not get the latest SHA from template (https://github.com/microsoft/AL-Go-PTE@main).
(Error was The remote server returned an error: (404) Not Found. Not Found)

Stack trace points to:

• GetLatestTemplateSha in CheckForUpdates.HelperFunctions.ps1: line 83
• DownloadTemplateRepository in CheckForUpdates.HelperFunctions.ps1: line 56
• CheckForUpdates.ps1: line 64

Environment details:

• AL-Go Actions version: v8.1 (SHA: 5628b94ecf2f1f06fd6eed86e25027a60ae93ab6)
• BcContainerHelper version: 6.1.11
• Runner: Windows Server 2025 (windows-latest hosted runner)
• Template URL configured: https://github.com/microsoft/AL-Go-PTE@main
• Template SHA stored in settings: 2b0291277622df06df2856bc05768be2ebb5a6b5
• Repo type: PTE
• The workflow was triggered via workflow_dispatch with directCommit=false and downloadLatest=true

Note: The repository calling this workflow is hosted on GitHub Enterprise Server (GHES), which
may be relevant if the GetLatestTemplateSha function uses API calls that require specific
authentication for accessing public github.com repositories from a GHES instance.

Expected behavior

The "Update AL-Go System Files" workflow should successfully retrieve the latest commit SHA from the
microsoft/AL-Go-PTE template repository on github.com, compare it with the stored templateSha,
and either update the AL-Go system files or report that no update is needed — completing the workflow
without errors.

Steps to reproduce

1. Set up an AL-Go for GitHub repository (PTE type) on a GitHub Enterprise Server instance using
   AL-Go v8.1.
2. Configure templateUrl as https://github.com/microsoft/AL-Go-PTE@main in
   .github/AL-Go-Settings.json or .AL-Go/settings.json.
3. Create a ghTokenWorkflow secret (GitHub App or PAT).
4. Trigger the "Update AL-Go System Files" workflow via workflow_dispatch with:
   • directCommit: false
   • downloadLatest: true
5. Observe the workflow fails at the "Update AL-Go system files" step with a 404 error from
   GetLatestTemplateSha.

Additional context (logs, screenshots, etc.)

Relevant log excerpt from the CheckForUpdates step:

TemplateUrl: https://github.com/microsoft/AL-Go-PTE@main
TemplateSha: 2b0291277622df06df2856bc05768be2ebb5a6b5
DownloadLatest: True
Get latest SHA for https://github.com/microsoft/AL-Go-PTE@main
The remote server returned an error: (404) Not Found.

Not Found

##[error]Unexpected error when running action. Error Message: Failed to update AL-Go System Files. 
Could not get the latest SHA from template (https://github.com/microsoft/AL-Go-PTE@main). 
(Error was The remote server returned an error: (404) Not Found.   Not Found ), 
StackTrace: at GetLatestTemplateSha, 
D:\a\_actions\microsoft\AL-Go-Actions\v8.1\CheckForUpdates\CheckForUpdates.HelperFunctions.ps1: line 83 
<- at DownloadTemplateRepository, 
D:\a\_actions\microsoft\AL-Go-Actions\v8.1\CheckForUpdates\CheckForUpdates.HelperFunctions.ps1: line 56 
<- at <ScriptBlock>, 
D:\a\_actions\microsoft\AL-Go-Actions\v8.1\CheckForUpdates\CheckForUpdates.ps1: line 64

Note: Prior to reaching the template, the workflow successfully accessed the template repository
to verify it exists (HTTP 200 with empty content). The 404 occurs specifically when calling
GetLatestTemplateSha, suggesting the API endpoint used to resolve the branch/SHA may differ from
the initial check.

[aholstrup1]

The repository is located on a self-hosted GitHub Enterprise Server?

Could you also try rerunning in debug mode and include the logs for that? That should include a bit more logging information.

[ChrisChristophers]

Hi, @aholstrup1

It's hosted on .ghe.com , but the runner is self-hosted.

Here are the full logs in debug mode.

logs_173471917.zip

If it helps i've tried theGHWORKFLOWTOKEN with the Github App and a PAT ( it resulted in the same error )

[Martijndo]

We just started looking into AL-GO for github also with Github Enterprise (hosted on ghe.com). This is one of the actions that also gives issues out of the box for me.

@ChrisChristophers How did you change the flow for Powershell Functions: FindLatestSuccessfulCICDRun and PullRequestStatusCheck, which seem to have hardcoded values for Github.com?
For now i made a clone and did some updates on a clone on our GHE environment, but perhaps you have a better solution.

[ChrisChristophers]

We have not changed any workflow since we are just in the process of setting this up. What we did do is mirror the AL-GO-PTE repo in our org and used that as a template but it did not solve the problem.

[aholstrup1]

GitHub Enterprise isn't something we currently support in AL-Go. At this time, we are building and testing AL-Go exclusively towards GitHub.com. In order to support GitHub Enterprise, we'd also need to be able to test AL-Go in a GitHub Enterprise instance to ensure that we don't break functionality whenever we release a new version of AL-Go. Unfortunately, this isn't a setup we have right now which is why we can't support it at this time.

Of course, that doesn't mean that we'll never support it. If this is something you'd like to see supported, I would encourage you to upvote this idea (#1999) as well as adding any context any context you feel is missing on the idea. That will help us assess whether this is something we should prioritize 👍