Managing deployment scripts in the process of continuous delivery
My question concerns deployment scripts in the process of continuous delivery.
Managing deployment scripts in the process of continuous delivery
My question concerns deployment scripts in the process of continuous delivery.
Managing deployment scripts in the process of continuous delivery
My question concerns deployment scripts in the process of continuous delivery.
Managing deployment scripts in the process of continuous delivery
My question concerns deployment scripts in the process of continuous delivery.
Managing deployment scripts in the process of continuous delivery
My question concerns deployment scripts in the process of continuous delivery.
Managing deployment scripts in the process of continuous delivery
My question concerns deployment scripts in the process of continuous delivery.
Branch per feature: What are the actual benefits (and risks)? [closed]
Closed 10 years ago.
Finding out which version of a file a line was added/changed
Is it generally possible while using source code management to figure out in what version of a file a specific line was added? If so, what SCM systems support this?
How to avoid old commits/PRs that are painful to merge?
We have a pretty good code review process, but there are couple of issues. The most annoying problem is merging. From time to time the number of stuff to merge grows rapidly and some of the commits are getting old. As a result, rebasing is a pain (conflicts).
Is it good to split big repository into smaller ones to have separate history/issue etc or keep it big? [duplicate]
This question already has answers here: Choosing between Single or multiple projects in a git repository? (6 answers) Closed 8 years ago. We are currently porting our huge svn repo to git and we are thinking to export subdirectories of repository, each one containing source code of independent binaries, documentation or robot tests, into separate […]