Replies: 7 comments
-
|
Sounds like a good idea. |
Beta Was this translation helpful? Give feedback.
-
|
Will there be future AL-GO support for auto-publishing source code documentation using aldoc.exe as part of the release action? (Incl. publishing documentation from the private source repo to a public github (pages) repo) References |
Beta Was this translation helpful? Give feedback.
-
|
Yes, working on that - #760 As you can see in the sample, it will create documentation for latest (work in progress) but also for shipped versions on the same site and you can determine how many versions you want. Will come in preview later this month is the plan |
Beta Was this translation helpful? Give feedback.
-
|
Nice work, looks promising 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Moved to roadmap |
Beta Was this translation helpful? Give feedback.
-
|
Hi @freddydk, this would help to solve one of the issues I have when assessing our move from Azure DevOps to AL Go. We have docs and a few other folders used by our internal tools that I'd like to exclude from CI/CD (they are changed quite often and won't impact BC so no need for us to run CICD). |
Beta Was this translation helpful? Give feedback.
-
|
I think it makes a lot of sense to be able to control paths-ignore - will have a look at what I can do. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Freddy and Team,
as I'm using GitHub Pages for documentation purpose, it would be great if the complete /docs path could be ignored in cicd.
Even if the docs folder (and subfolders) mainly contains .md files (which are already ignored), there may be also other filetypes which now may trigger an unnecessary start of cicd workflow.
/docs is btw a standard GitHub folder to built GitHub pages from selected branch.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions