dodexahedron

Current work items I'm thinking of doing, for this and other questions/comments etc: - On main project README.md, in the build instructions, add all commands to do it in the...

> some tome you wrote That doesn't sound like me _at all!_ 😇 😅

> Also, @dodexahedron , the Publish github action for v2_develop is not working. See > > https://github.com/gui-cs/Terminal.Gui/actions/runs/8989765575 > > Can you please advise? This looks like a dependency issue, likely...

Yeah, the publish action is going to need changes for sure, and probably should be split regardless, since the build isn't _really_ the same anyway, for v1 vs v2. For...

I've got a much more robust solution in the works which also tests on windows and mac as well, among other things. But that's certainly plenty as an immediate fix...

Oh I did have a quick question (though I'm sure I can find it myself). What, specifically, is that gitversion step/tool doing? Is it just substituting parts of the version...

Oh. I'd suggest, for formality's sake, to add a `Remove-Module Terminal.Gui.PowerShell` as the final step, to avoid interference with other possible jobs, especially on forks and such.

And is the no-restore a good idea for the build? The Build-Analyzers part won't necessarily cause all of the dependencies from other projects to be restored, if it doesn't specify...

RE: The gitversion tool: I noticed the Release.ps1 script in root already started to do that sort of thing. Something similar either in PowerShell or just in the workflows themselves...

Bah. For a few reasons, I can't test these properly without cloning the repo to a new sandbox that isn't a fork. So, in the interest of time, I'm reducing...