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.
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
Questions about Git should be asked in Software Development. This is a case of bringing the question to the experts.
Git is a general purpose version control system, that can be used to version any type file, not just code. However, it is very popular with programmers, and many features were designed with code in mind.
Currently, the git tag has:
- 45 posts on Software Development
- 5 posts on Power Users
- 3 posts on Linux
This is not unique to Codidact. Taking the more popular StackExchange as an example:
- 153k on StackOverflow
- 2.7k on Superuser
- 1k on Unix
It seems like people instinctively gravitate to asking about git in the coding section.
(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.
0 comment threads