[releases/26.4@c2fca3f] Update AL-Go System Files from microsoft/AL-Go-PTE@preview - 87ad9f9 / Related to AB#539394#6738
Merged
business-central-bot[bot] merged 1 commit intoreleases/26.4from Feb 19, 2026
Conversation
…o-PTE@preview - 87ad9f9 / Related to AB#539394
business-central-bot
bot
added
the
Automation
github-actions
bot
added
Build: Automation
mazhelez
approved these changes
Feb 18, 2026
aholstrup1
approved these changes
Feb 19, 2026
business-central-bot
bot
deleted the
update-al-go-system-files/releases/26.4/260218124045
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
preview
Note that when using the preview version of AL-Go for GitHub, we recommend you Update your AL-Go system files, as soon as possible when informed that an update is available.
Issues
The default pull request trigger is changing
AL-Go for GitHub is transitioning from the pull_request_target trigger to the more secure pull_request trigger. This is a step we are taking to make AL-Go for GitHub more secure by default. If you are used to working from branches within the repository you may not notice any difference. If you get pull requests from forks, those pull requests will no longer be able to access secrets. If that is blocking for your repository, you will need to update your settings to use the pull_request_target trigger.
How do I revert back to pull_request_target?
Add the following setting to one of your settings files and run the Update AL-Go System Files workflow:
Related to AB#539394