Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Where should I ask git questions?

Parent

Where should I ask git questions?

+5
−0

Where should I ask questions about Git?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+6
−0

(Speaking personally, not for the team.)

People using git are usually using it in a software context, and Software Development's scope is intentionally broad, so they definitely fit here. This is where most of them end up. That's fine.

Questions about git can be on-topic elsewhere too. Communities overlap; think of it as affinities, not the Dewey Decimal System where each thing fits in exactly one place. I once answered a question about source control (not specifically git) on Writing and in context that made sense. In general, people want to ask questions in places they're already active and with contexts they already understand. If the question isn't off-topic, that seems fine to me. Every time someone hears "no, go over there instead", there's a chance the person will just punt instead -- we don't get the question and the asker doesn't get answers.

It's also fine to leave a comment letting the asker know that there are other places to find git questions (and people who can answer them). Maybe the person decides to come here, or maybe the asker already got an answer that was good enough. Let's help our communities work together and meet people where they are, when possible.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

"git for X" (2 comments)
"git for X"
matthewsnyder‭ wrote 5 months ago

I think your example about writing is a great point. I was thinking that if there are multiple places to ask git questions, then every time you ask a new one, you have to think about which one it goes in. However, actually it becomes obvious if you remember context. "git in the context of writing" obviously belongs in writing, "git in the context of coding" obviously belongs on SWdev, etc.

Monica Cellio‭ wrote 5 months ago

Or, I suspect, the asker's thinking is: I'm writing my novel, saving "v37" etc isn't really a good way to manage checkpoints, also I want to be able to easily jump back to a good state from before I added that doomed plotline... how would I use source control to make my life easier?

In other words: there's already a context of a writing problem or a programming problem or a distro-management problem or whatever, and you're going to ask your other writers/programmers/sysadmins for help. And source control fits here, so you ask here (wherever "here" is).

Skipping 1 deleted comment.