[Bug]: Support for localDevEnv.ps1 using Internal Repository

[peterelmqvist]

AL-Go version

7.0

Describe the issue

We are using AL-Go in an internal repository. Using localDevEnv.ps1 does not work since it assumes a public repository.

Downloading Github-Helper.psm1 from https://raw.githubusercontent.com/{Organisation}/AL-Go/Actions/98ed7ec23cd1eabc6509e55d3467b1da588f4223/Github-Helper.psm1

Error: Response status code does not indicate success: 404 (Not Found).

Expected behavior

Internal respository for AL-Go is supported so the localDevEnv.ps1 should have support for this as well.

Steps to reproduce

Fork AL-Go as an internal repository
Create an PTE in a repository
Try to run localDevEnv.ps1 to create a local DEV-environment

Additional context (logs, screenshots, etc.)

No response

[aholstrup1]

Out of curiosity, could you share why you decided to create a private fork of AL-Go? Are there specific functionalities or features you're looking to add or modify?

[freddydk]

BTW - Internal respository for AL-Go is not supported today - we have a few partners looking at whether it is possible to do so and we might fix things to make it possible, but it adds a lot of problem to our support if people detach AL-Go from microsoft/AL-Go

[peterelmqvist]

We would like to use the public AL-Go repository, but we are waiting for the Indirect Template-feature. This and also the ability to fix issues that have not been resolved yet, like App Auth in certain scenarios is the reason for us having our own repository.

That being said, we are happy to contribute to AL-Go and create PRs in order to reach a situation were we can use the public repo instead.

[mazhelez]

As using an internal AL-Go repository isn't a supported scenario today, there isn't anything to address.

We'll try to evaluate supporting such cases as part of #853