331–340 of 353 posts
When will we get repo-specific tokens? That's what I really want. As-is, I've just created extra special purpose github accounts, but that's a bad solution IMO.
You mean like deploy keys? https://docs.github.com/en/developers/overview/managing-depl...
Earlier quoted context omitted.
I also have found teaching someone how to be even marginally capable of contributing to a Github project from scratch to be a very time consuming and frustrating thing. Think, having your graphics designer able to make commits, or having someone who only wants to update docs. The worst part is the "easier" solutions are actually just footguns in disguise, as soon as they accidentally click the wrong thing and end up…
> The worst part is the "easier" solutions are actually just footguns in disguise, as soon as they accidentally click the wrong thing and end up with a detached HEAD, a few commits ahead and behind the REMOTE, and halfway through a botched merge Is graphic designer even going to be able to merge things in their files? It seems that "overwrite my files by data in repository" "apply my changes with message" are all wha…
Another extremely common pain is trying to "delete" a local commit.
Earlier quoted context omitted.
Then stop paying for it.
Stop paying for what? I don't pay for GitKraken because I can't justify subscribing to software that doesn't materially change. The risk is that they have to keep "doing stuff" to justify a subscription and we will end up with a new email client.
Ok I'll admit it. I'm the dingus who is still using https and login/password. It's how I learned to use it years ago and since I only ever access GitHub via cli it's all I've ever learned. I don't program anything complex and I've never put anything secure up on GitHub (it's public, after all, so i had the expectation that all info on there is insecure). I don't understand why this is being deprecated when it's the d…
Earlier quoted context omitted.
> What do you expect? That people without prior knowledge or experience just pick up source control in seconds? I mean, ideally, that'd be great. I don't think there's any fundamental reason things can't be this way, many of these complexities are completely incidental, rather than inherent. > Is it really too much to ask a newcomer to invest some hours into learning something these days? No, but when I'm learning so…
I get the argument but I disagree. Git is meant for software developers on projects complex enough to warrant using SCM. Using SCM for teaching development to newbies is already adding unnecessary complexity (even in a collaborative setting, flows are complex enough to distract from more fundamental topics). If you're a software developer getting to the point where using git is needed you should absolutely know the c…
Earlier quoted context omitted.
I just have non-devs use the browser interface and this seems to work for text edits and image uploads and stuff. And some statisticians and stuff only know how to use the GitHub desktop client and that works ok for 99% of them. Drives me crazy because I only use cli and struggle to help when they get blocked with the client.
The cynic in me says they’re taking advantage of the fact that the web UI is a lower friction experience to drive more people towards Codespaces (which are not cheap, by the way).
Earlier quoted context omitted.
You could always use "Deploy keys" which are per-repo read-only SSH keys. You could set up multiple repos with the same deploy key and use the private key in GitHub Actions secrets.
This won't work as a deploy key can only be used in one repo.
Earlier quoted context omitted.
> Git is meant for software developers on projects complex enough to warrant using SCM. I and most developers I know use git or similar for projects of any size, often even if it's "just" a single file or a "one-off" change (because it rarely stays that way). I would have agreed in the days when Subversion was the closest you could get to "easy version control" but these days in my eyes "the point where using git is…
I think this way overestimates the value of both Git and source control in general for a lot of projects. Is this the result of the now common development methodology of using as many dependencies as possible or something?
Earlier quoted context omitted.
Sounds a lot like a hoop. With password I can use any device with git installed to pull and push from/to github repos. Now I'd need a hack like this on top. I prefer less tools to more tools. Probably a losing battle given how the field is developing.
GCM Core is installed out of the box with official git installer on Windows. Several Linux distributions at this point include it as well. On macOS it is a simple brew install away. git itself was built as an agglomeration of multiple tools bundled together and GCM Core is right on the borderline of a tool always included in the git distribution anyway on some platforms and needs to be installed on others. It's likel…
Sorry, but I still hate it. I want less software, not more.
So now I can't use git client on github repos anymore without carrying a device that has some impossible to memorize key or token on it? I hate it. I don't care much for the slight chance that someone gets into my github account. I care a lot more that now I have to jump hoops to get into my account myself. There's more to things than security.