New answers tagged

0

There's no easy answer to this, get your repos too big and every branch becomes huge over time, make it too small and you end up doing a lot of administration. Many smaller repos has my preference, but only after creating some support scripts to do the administration for you. For example, to pull all repos: ls -d **/ | xargs -P12 -I{} git -C {} pull Also ...


1

This is something I also struggle with. I can tell you from experience it depends on the type of application and the tech stack being used. The short easy answer is that having everything in one repo is usually not the wrong or hard way. Breaking things out often doesn't offer many benefits but again it will all depend on your CICD engine and what kind of ...


1

I had a similar need and I did it as below. In my case it is archived and published differently but I think you get the main idea. - task: PowerShell@2 displayName: 'Get version number' inputs: targetType: 'inline' script: | $VERSION=([xml](Get-Content **\MyApp.csproj)).Project.PropertyGroup.Version Write-...


Top 50 recent answers are included