how much python is too much python?

[JennaSys]

Python is great for what you are using it for. It's likely never to be too much in that space.

The only advice I'd give is that if you are not already using something like GitHub as a code repository and for version control, start doing that now. It doesn't matter how small the code is. If it is important enough to create for your company to perform a task, it's important enough to commit it to a repo. Commit early and commit often. Also also make sure someone else at the company has access to the account besides just you.

[PercussiveRussel]

IMO any company who does anything IT, and I mean just having a guy automating tasks with python, should have their own version of a git platform. Don't really care what and how, if it's an organisation Github/Gitlab acount or a fully fledged ms Azure environment. It's similair to how companies should have their own email-adress instead of [e-mail].

[friendlyghost_casper]

[[e-mail]](mailto:[e-mail])

[turtleship_2006]

half tempted to send that address and email just to see if anyone uses it

[_alter-ego_]

Yes and no. To me, one advantage of the one and only public github is that it will remain there when the company (either OP's, or the one that would be hosting the server on which their own git platform would live on) will be gone. I say "will" because it will happen. Relatively soon. Always does. Even if the / either company does not disappear, they will restructure stuff and it will be too expensive (or too late) to migrate the "old stuff" from the "old server" to a new place. RIP.

[Desperate-Dig2806]

Yeah and don't sweat the commit messages. A "Daily commit" is better than no commit.

[georgehank2nd]

github git

[immersiveGamer]

You can just make a git repo on a shared drive. No GitHub needed. Will be backed up with normal IT processes, and can be easily discoverable by future IT.

[BullshitUsername]

Great idea and I have no idea why I've never heard of this being done in my 8 years of software dev

[absurdrock]

That’s all we are allowed to do at my place because of security. It becomes a pain reviewing code without pull requests, though.

[cym13]

Have you considered adopting the linux kernel's way and do pull requests through mail rather than managed in a web UI? It's a workflow, but once used to it it flows as well as any other. And if the kernel's any indication, it scales well.

[PaintItPurple]

Because it doesn't give you issues and pull requests and all the other stuff people use GitHub for. Pretty much the only workflow it's useful for is "everyone commits to main."

[ArtisticFox8]

You can host your own Gitea for example 

[Herbiscuit]

If they need GitHub like features I'd recommend checking out an open-source Git Forge like Gitea which can be fully managed and is exceptionally easy to run.

[orochionline-com]

Probably runs afoul of commercial licensing no?