Skip to content

Conversation

@omajid
Copy link
Member

@omajid omajid commented Jan 29, 2026

Some consumers of the VMR source build consume the git archive generated source tarball. Without this change, the source tarball doesn't include the content/../.gitattributes file, which makes dotnet new gitattributes non-functional.

Fixes: #52307

Some consumers of the VMR source build consume the `git archive`
generated source tarball. Without this change, the source tarball doesn't
include the content/../.gitattributes file, which makes `dotnet new
gitattributes` non-functional.

Fixes: dotnet#52307
@baronfel
Copy link
Member

/backport to release/10.0.1xx

@baronfel
Copy link
Member

/backport to release/10.0.2xx

@github-actions
Copy link
Contributor

Started backporting to release/10.0.1xx (link to workflow run)

@github-actions
Copy link
Contributor

Started backporting to release/10.0.2xx (link to workflow run)

@github-actions
Copy link
Contributor

@baronfel backporting to release/10.0.1xx failed, the patch most likely resulted in conflicts. Please backport manually!

git am output
$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Patch format detection failed.
Error: The process '/usr/bin/git' failed with exit code 128

Link to workflow output

@github-actions
Copy link
Contributor

@baronfel backporting to release/10.0.2xx failed, the patch most likely resulted in conflicts. Please backport manually!

git am output
$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Patch format detection failed.
Error: The process '/usr/bin/git' failed with exit code 128

Link to workflow output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[10.0.101]dotnet new gitattributes emits no file

2 participants