8
votes
Who is the potential audience of a commit message?
Good commit messages are underrated, in my opinion, kudos to you for trying to improve in this aspect.
I think the primary audience for commit messages are other developers. There might be other ...
- 311
5
votes
Accepted
Who is the potential audience of a commit message?
There can be several potential readers with different expectations:
A reviewer going over your code will read the commit message for context and to understand the rationale for the new code.
Your ...
- 9,545
4
votes
Why does Meta (Facebook) use mono-repo in their source control?
The closest thing to an official answer:
Our code base has grown organically and its internal dependencies are very complex. We could have spent a lot of time making it more modular in a way that ...
- 14.8k
4
votes
Accepted
Mercurial topology in three stage implementation
I can see the value of having multiple local working copies for various reasons, but I don't see what the point of the middle "tier" is if everything pictured is a true clone.
Having multiple working ...
- 496
4
votes
When to separate a project in multiple subprojects
This post is a bit old but I would like to contribute. Whilst your back-end doesn't really know about the front-end the front-end needs to have requests matching the back-end's API. If you consider ...
- 141
2
votes
Accepted
Source control utilizing single, remote development server, with "local repository" not on dev's machine
Windows Server is perfectly capable of handling something like this with some manual intervention (or better yet, PowerShell scripts). I'd suggest using Git, because I know it can handle the situation ...
- 1,828
2
votes
What is the point to namespaces in branches in git?
Git doesn’t use namespaces for branches.
A legal Git ref (like a branch) is allowed to look like a filepath as
seen on Unix systems like Linux, which means that e.g.:
feature/xyz is allowed
feature/...
- 364
1
vote
Any reasons not to use multiple version control systems?
You can keep your patches separate in Git: do each one on its own branch, then merge them in selectively as desired.
1
vote
Source Control Release Management: Simultaneous Releases with Different Configurations
The problem with removing a feature by changing the source code is that you have no guarantee you haven't broken some other feature due to some shared code.
If you need to switch features on and off ...
- 79.8k
1
vote
Introducing version control with a simple pull request workflow
While there are some nice GUI's other than the one included in visual studio for git it would still be best to understand the inner workings. Since this is all focused around database scripts and ...
- 107
1
vote
Accepted
Best practice to revive and update old branch?
You want (in common) merge default to feature (resolving a lot of possible merge-conflicts).
Slightly different way:
convert all changesets of feature branch into the set of MQ-patches
create new ...
- 1,937
Only top scored, non community-wiki answers of a minimum length are eligible