Brandon Olin

I like it @lukas-lansky! I've been thinking it would be nice to get a visual of dependencies. It should also be an option to display the tree without actually running...

Thanks for the contribution @dmarlow! Removing the ability to specify multiple tasks is indeed a breaking change. I haven't went over the code in detail yet but did you look...

New features ARE being added now. I'm reopening this as I think it's a good idea. I personally find the difference between `properties` and `parameters` in psake to be confusing...

Thanks for the issue @fgodskesen. Indeed, the parameters _should_ be PascalCase. It's been on my TODO list for a while. I'll get it prioritized for the next release.

PS shouldn’t find the MAML XML so will revert to the comment-based help on all the functions. Now that we have the help in markdown files via PlatyPS, we can...

Yes, the comment-based help attached to each function should be removed as that will exist in the PlatyPS MD files. We'll need to add a couple of tasks in `build.ps1`...

@Splaxi Can you expand on what the purpose of tags would be? Would it be for grouping tasks and executing all tasks with a certain tag? A list of scenarios...

Nope. Haven't seen this. Thanks @Jaykul!

@nbarnwell I haven't dug into _why_ this regression happened (looks like it's been awhile) but if you use `$script:variable` syntax in `Properties`, subsequent tasks can modify the value. ```powershell Properties...

That's a good question @wwestrop. How do you think this behavior should work? To my mind, it should be: 1. If called from pwsh, run psake in pwsh 2. If...