File prefix

Picture this: You're knee-deep in a project, and you need a clean slate to work with. What do you do? You whip up a temporary playground – a fresh directory where you can toss all your project files without fear of messing up the originals.

But here's the kicker – you've got this nifty trick up your sleeve. You rename these files with a special prefix, like leaving breadcrumbs in a forest. Your go-to prefix? 'Gash'. It's your secret code that screams, "Hey, these files are just for now – feel free to bin them later!"

It's like creating your own little sandbox where you can build, break, and experiment to your heart's content. Pretty smart way to keep your work organized and your original files safe, if you ask me!

Here’s some Microsoft PowerShell code to rename files with our selected (preferred) prefix:

# Get all files in the current directory, excluding those that already start with 'gash'

Get-ChildItem -File |

    Where-Object { $_.Name -notmatch '^gash' } |

    Rename-Item -NewName { 'gash_' + $_.Name } -WhatIf

Renaming files that are in use by running processes can cause issues. Ensure that the items you're renaming are not actively being used by other applications.

WhatIf (risk mitigation) parameter: Use the -WhatIf parameter to simulate the rename operation without making actual changes. This can help you verify the expected outcome before committing to the change.

Remember to remove the -WhatIf parameter when you're ready to actually perform the rename operation