In a repository, there’s a dev branch and a main branch. There’s been a few commits in the dev branch and I want to take a specific commit to the main branch. I’m using Azure DevOps/GitHub Desktop and everything I’ve tried, it appears to take all the commits and not just the specific commit. I can’t push directly to main; I need to use a pull request. How can I merge a single commit?

In a repository, there’s a dev branch and a main branch. There’s been a few commits in the dev branch and I want to take a specific commit to the main branch. I’m using Azure DevOps/GitHub Desktop and everything I’ve tried, it appears to take all the commits and not just the specific commit. I can’t push directly to main; I need to use a pull request. How can I merge a single commit?

Environment: Azure DevOps Server 2022.0 with Windows-agents

As the title says, I have a git repo with a branch that I have set branch policies on.

I have a repository in azure devops that i cloned in visual studio 2019.

i want to create pipeline that will show prod stage only for release/ branches. I developed yaml like this:

I want to modify this existing pipeline (which publishes to a test server) to only get files modified on the current branch. The issue I’m running into right now, is if one person pushes to branch A and the other to branch B, the pipeline overwrites all of the files with files from branch B, regardless of whether or not they were actually modified. I tried updating the checkout to fetchDepth: 0, but this didn’t work.

I want to modify this existing pipeline (which publishes to a test server) to only get files modified on the current branch. The issue I’m running into right now, is if one person pushes to branch A and the other to branch B, the pipeline overwrites all of the files with files from branch B, regardless of whether or not they were actually modified. I tried updating the checkout to fetchDepth: 0, but this didn’t work.

In addition to our current branch policy pipeline, which performs a build of the proposed branch to be merged and runs unit tests within build, I would like to add an extra step which then simulates the resultant merge before integration with main code. If the 2nd-level build and test also passes, then the PR should be able to be completed (post normal Peer/code review). As we currently have several occasions where bugs/test failures are only being picked up after merge.

I have a commit A, which consists of 1000 modifications/creations/deletions.
Basically 90% of creations/deletions are moves.
I can indeed see it when I run git status --find-renames.