Stop producing the git-info files
#4858
Assignees
Comments
Yes, I think that's the best tactical solution. Same could apply to #2428. If the entry exists, update it. If not, don't update it. |
|
Oh no, the git-info came back because the commit the ff branch is based on an older commit which still has these files.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Similarly to #2428, we can stop producing the
git-infofiles as they are no longer needed.We should still make sure that the servicing branches can use new darc and produce these files.
Though the
8.0branches might be stuck on an older version ofdarcalready.The
9.0branches recently got updated: https://dev.azure.com/dnceng/internal/_git/dotnet-sdk/pullrequest/50250So we might need to keep the support because of these.
Maybe it could produce these when the folder/file exists and ignore it if it doesn't,
Goal
Make darc not update the
git-infofiles when they don't exist.The text was updated successfully, but these errors were encountered: