Skip to content

Latest commit

 

History

History
31 lines (16 loc) · 2.11 KB

UpdateAlGoSystemFiles.md

File metadata and controls

31 lines (16 loc) · 2.11 KB

Update AL-Go system files

Prerequisites: A completed scenario 5

  1. Every time a CI/CD pipeline runs, it checks whether there are updates to AL-Go system files. AL-Go System files are scripts in the .AL-Go folder and workflows in the .github folder. Looking into the details of the Check for updates to Al-Go system files, usually looks like this

    CI/CD

  2. In VS Code, try to modify the LocalDevEnv.ps1 file, stage the change, commit and push.

    localdevenv

  3. Now there is a difference. AL-Go doesn’t support that anybody changes the AL-Go system files and will warn about these changes. The CI/CD pipeline, which kicked off when pushing the change, tells me about this.

    summary

  4. To update the AL-Go system files using the Update AL-Go System Files workflow, you need to provide a secret called GHTOKENWORKFLOW. Please use this walkthrough to create this secret.

  5. On github.com, under Actions in your project, select the Update AL-Go system files workflow and choose Run workflow. Leave the Template Repository URL blank and choose Run workflow.

    update

  6. Inspect the pull request and see that it indeed reverts your change to the LocalDevEnv.ps1 file.

update

  1. By default, this workflow will apply any updates to the workflow files (in .github\workflows) or system scripts (in .AL-Go) from the template repository used to spin up the repository. If you want to change branch or template Url, you can specify the templateUrl@branch when you run the workflow.

back