“Just setup github oidc provider as idp in aws iam. There’s a managed workflow from aws that handles signin for you and you just have to create a role and give it permission to what you want”
“We fully automated are it. Terraform creates the UAMIs and federated credentials in Azure, GitHub Actions syncs the Client ID, etc over to the repositories. Fully automated.”
“Github copilot uses much less, it only burns like 3 dollars worth of tokens at a medium sized task, but for example claude code usually burns 2 or 3 times as much. But claude code output is usually better so I prefer to use that one until I ran out of my monthly API tokens at my company.”
“I'm currently evaluating GitHub Copilot vs. Claude Code for our team. We could use either, but for us there's a slight difference in cost per token (Copilot with Anthropic models vs.”
“Why is this a relevant concern if your using GitHub Enterprise? The general data security clauses cover you for use of those otherwise forbidden models.”
“tldr; If the above switch is enabled, when new models, or models that were never specifically enabled or disabled, will become available through Github Copilot.”
“There was a change in AI Controls for enterprise. The default behaviour was that models that had not been enabled would be «delegate to default policy» and the default policy seems to be enabled.”
“You still have to use GitHub storage to put something there for the authentitcation to work, there will always be a passing of valid variables to the workflow, the tricky part is to reduce the blast radio in case off leakeage.”
“This is not entirely true, you can use a docker image inside the Github Actions Ubuntu VM or a sysroot but that is beyond even most expereinced app devs to setup.”
“Im not gonna continue fighting over simply trying to do something that is done everyday across GitHub. this is getting ridiculous and alot of public repos take weeks for your changes to get merged im doing these things for a reason from a development standpoint?”
“If it is triggered by a PR or even a push (which not many people usually do), it’s best to have "concurrency" set up. This way, you don't spam the runner and overload it.”
“also packages: write permission scoped at the job level is the right call, a lot of people just set it at workflow level for everything, which is broader than it needs to be.”
“It finds a lot of stuff that a lot of people wouldn't even think about when it comes to security issues. I think that alone is worth going with Github Copilot but that's just me.”
“Using GitHub/git is great for any development, period. GitHub is great as a source for the repo (git is not GitHub), but you can also use GitHub Actions for things like deployment (and other continuous integration things like linting/testing/build pipelines etc)”
“Of course copilot is cheaper. Because its shit. We get everything from MS for pennies. I tried to get rid of 365 and non github copilot in my company but its just too cheap.”
“I've been a fairly heavy Copilot user, and haven't heard a thing about the company paying more or high costs. At this point I'm chalking that up the subscription working like insurance.”
“With all these billing changes why do enterprises continue to lock in with GH Copilot when there’s also Claude Code or Codex which if we’re honest are cheaper if you break it down in terms of outcome and quality ?”
“setup github pipeline only for the active theme, not for the whole wordpress.. and that enough will make work smooth you never imagined.. I literally didn't used filezilla or file manager from last 2 years”
“Github Actions handles the deployment on the dev server through a fast-forward pull of the current RC. This history should always flow to the next RC.”
“I have a sage 11 theme hosted on GitHub. When I push to the deploy branch, it fires a GitHub action that runs the build process then sends the files over SSH. Hosting is agood ole namecheap server with cpanel.”
“I use a version controller function in the themes, it checks on github if there is a most recent version of the themes and if it is the case you can just update it like any other theme or plugin.”
“Everyone on their own self-hosted git servers, zero collaboration.Everyone sticking to Github, then a year or two from now Github resolves their scaling issues and the competitors miss their window of opportunity to disrupt”
“It ridiculous, Codeberg did the same. I get why, really, I do, but it's creating a severe damage that will be abused by a third evil actor that will take over the wasteland of GitHub and GitLab by creating a service that will allow anything (until it is enshittified of course)Outcome?”
“> GitHub is going the wrong way, but there really is nothing workable for open-source projects except GitHub.Open source projects existed just fine before GitHub, and they will exist just fine if they choose to move off GitHub as well.”
“It really is a testament to the power of mindshare and vendor lock-in. Git is GPL-licensed, the format is a de-facto standard, the commits and tags live in an on-disk format, merging and collaboration doesn't require a server, and yet somehow we still managed to end up with a centralized system with GitHub at the center.”