I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I'm not really sure how this would work, because your idea of "Fork / otherwise clone the repository" relies on some kind of basic system being installed already, like WSL or Git Bash (full disclosure, I've never used Git Bash but people go on about it like it's good).
After that, everything that's standard on other OS will (should) work the same way, and everything that's Windows-specific will need a whole different kind of installer.
Of course you can't just write a set of scripts to install any OS, be that Linux, Windows, or anything, without any tools. If all you have is a terminal prompt with no internet access, and no editor installed, it's gonna be tough to write a script of scripts to GitHub.
I have no idea why you would assume WSL, or Git Bash would be in any way manner or form necessary for any of this, or what you're on about "other OSes", this is a tool for Windows and is pretty much completely unusable for Linux or others, and their tools are not particularly useful for Windows because Windows does not run them by default and they have no understanding of e.g. Windows registry. I created a tool that can take your fresh Windows installation from the first time you log in, to having all the tools you want in it, with much of the configuration already done, with one copy & paste to a PowerShell terminal.
What you do is, using your existing working environment that you write your dev.to comments on, you set up the repository with the configuration for how wish your machines to be, and then run the commands on the machines you want configured. This works both for making changes on your currently running machines, by giving you access to tools that weren't as easily available before, some sensible defaults, as well as a backup for your settings for whenever you eventually happen to need a reinstall or new hardware.
It also works especially well when you have a number of machines that you'd like to sync up, as you just have to push your changes to the repo and they will get applied on all your machines.
The initialization commands do not depend on any kind of WSL, Bash, Git, or anything else than plain Windows PowerShell, and can configure a large number of things and save a lot of time even when you have an existing working setup.
Btw this "standard environment" basically would already work out of the box, and doesn't need you to do anything but run the commands - though you shouldn't because of the reasons mentioned in the repo.
Forking on GitHub is about 1-2 clicks, and that's all you need to make it your own and safe to use.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not really sure how this would work, because your idea of "Fork / otherwise clone the repository" relies on some kind of basic system being installed already, like WSL or Git Bash (full disclosure, I've never used Git Bash but people go on about it like it's good).
After that, everything that's standard on other OS will (should) work the same way, and everything that's Windows-specific will need a whole different kind of installer.
Well, you should maybe read the usage guide then.
Of course you can't just write a set of scripts to install any OS, be that Linux, Windows, or anything, without any tools. If all you have is a terminal prompt with no internet access, and no editor installed, it's gonna be tough to write a script of scripts to GitHub.
I have no idea why you would assume WSL, or Git Bash would be in any way manner or form necessary for any of this, or what you're on about "other OSes", this is a tool for Windows and is pretty much completely unusable for Linux or others, and their tools are not particularly useful for Windows because Windows does not run them by default and they have no understanding of e.g. Windows registry. I created a tool that can take your fresh Windows installation from the first time you log in, to having all the tools you want in it, with much of the configuration already done, with one copy & paste to a PowerShell terminal.
What you do is, using your existing working environment that you write your dev.to comments on, you set up the repository with the configuration for how wish your machines to be, and then run the commands on the machines you want configured. This works both for making changes on your currently running machines, by giving you access to tools that weren't as easily available before, some sensible defaults, as well as a backup for your settings for whenever you eventually happen to need a reinstall or new hardware.
It also works especially well when you have a number of machines that you'd like to sync up, as you just have to push your changes to the repo and they will get applied on all your machines.
The initialization commands do not depend on any kind of WSL, Bash, Git, or anything else than plain Windows PowerShell, and can configure a large number of things and save a lot of time even when you have an existing working setup.
The basic usage information is at github.com/Lieturd/aperture-control
List of premade "recipes" for things that you can easily automate with it are available at github.com/Lieturd/aperture-contro...
Btw this "standard environment" basically would already work out of the box, and doesn't need you to do anything but run the commands - though you shouldn't because of the reasons mentioned in the repo.
Forking on GitHub is about 1-2 clicks, and that's all you need to make it your own and safe to use.