How should I safely deploy my commit when there are 51 old undeployed commits before it?
Yesterday, I was trying to add a feature to my company’s app. I am only an intern, so I wanted to be extra careful. The app is deployed to Azure App Service through Azure DevOps.
After I finished the feature and tried to push my changes, I noticed that the last successful deployment in the pipeline was around nine years ago. I also found a commit that has been stuck in the pipeline queue for almost nine years.
Between the last deployed commit and my new feature commit, there are 51 undeployed commits. None of these commits were made by me, and all of them are quite old, at least five years old. Because of that, I do not want those commits to go into the pipeline, since I am not sure what might happen if they are deployed.
However, I still want my own commit to be deployed. What operation would you recommend in this situation?
My idea is to copy the current master branch to a new branch, reset the 51 old undeployed commits, then apply my own commit and run that branch through the pipeline. Would this work safely?