Questions tagged [version-control]
A programming discipline for tracking, storing and retrieving revisions of source code.
978 questions
- Bountied 0
- Unanswered
- Frequent
- Score
- Trending
- Week
- Month
- Unanswered (my tags)
4
votes
5
answers
532
views
What is the current definition of a Mono-Repo
Facebook famously made a post about using a "monorepo" and for a while it seemed like this approach would take over from standard, separate out the code into multiple source controlled "...
2
votes
3
answers
153
views
Should a web framework / template like Admin-LTE be put in source control alongside our own code?
My team does predominantly back-end work in C#, with a smattering of front-end web development using Angular. We're starting a new website project, based on the Admin LTE framework / template. This is ...
4
votes
1
answer
187
views
Maintaining software for different versions of Ubuntu
I have some software intended to work on both Ubuntu 22 and Ubuntu 24, but due to differences between the distributions, it doesn't function properly on Ubuntu 24. Given this context, what is the ...
1
vote
6
answers
306
views
How to manage common library dependencies to prevent cross-application breakage?
Note: The question was heavily rewritten after the comments it received.
I work on a team that develops embedded software for various in-house devices. Each device hosts multiple "bare metal"...
19
votes
7
answers
5k
views
Debugging a performance issue, do I commit the timing code?
I am working in small company, having a lead position in a group of 5. We are developing a C++ application. One requirement is that it needs to run fast.
Today, I noticed one function, say f1(), and ...
14
votes
8
answers
4k
views
When is it acceptable to commit directly to main/master?
Working with Git, I’ve often heard that committing directly to the main (or master) branch is generally discouraged. Instead, many teams adopt workflows where all changes are made in separate branches,...
2
votes
3
answers
104
views
Planning Dynamic Patient Charts with Version Control and Historical Accuracy - Temporal Versioning or JSON
I'm working on a project for our healthcare clinic's software and could use some guidance. For regulatory and historical purposes, patient charts need to remain as "static" records—...
2
votes
2
answers
828
views
What are the pros and cons of using cherry-pick versus merge for release management? [closed]
What are the pros and cons of using cherry-pick versus merge for release management?
Background
We have a dev branch, and just created a release1 branch from it. Folks will commit relevant content to ...
18
votes
7
answers
5k
views
Is there anything wrong in reordering commits?
So, in many software you can do that easily using the mouse:
Although very useful, they aren't in chronological order anymore.
Is there anything wrong in doing that?
0
votes
2
answers
4k
views
Why does Meta (Facebook) use mono-repo in their source control? [closed]
Meta maintains all their code in a single repository and initially used Git. Due to performance issues attributed to the repo's size, they consulted Git's team, who suggested switching to a multi-repo ...
0
votes
2
answers
218
views
Source Control Design for Proprietary Logic which includes Obfuscation
Problem:
There are proprietary algorithms that developers who are actively working on a project will need to call but they should not see the underlying logic. They need to be stored in an area of ...
9
votes
3
answers
7k
views
How should source code unit tests affect semantic versioning?
I recently started using Semantic Versioning.
Due to conflicts with my previous versioning convention (which I created myself), I am very confused about versioning unit tests as part of the public API....
11
votes
11
answers
7k
views
Where to keep the code that I do not want in the main?
I made some changes that, after testing, I decided not to use for now.
Thus I don't want them in the main branch.
However, I don't want to discard them altogether (maybe I will need them later?)
What ...
2
votes
2
answers
765
views
Where to tag releases to achieve "build-once, deploy-everywhere" using GitFlow?
TL;DR: Using GitFlow, which commit do you tag to identify the build of your next release? If you tag the merge commit on main, you'll need to rebuild and deploy something you didn't test on QA (and ...
1
vote
1
answer
761
views
Git Branching and Merging Strategy for Feature-Oriented Release Process
We have multiple developers contributing to a project, using Git as our repository. We have a QA branch that matches our QA environment and a master branch that matches production.
Features can be in ...