A commit created by Dependabot contains a file treating unchanged parts as changed in the diff

[Takym]

Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

GitHub Actions

Package manager version

No response

Language version

No response

Manifest location and content before the Dependabot update

https://github.com/YigtyORG/TakymLib/tree/master/.github/workflows

dependabot.yml content

https://github.com/YigtyORG/TakymLib/blob/master/.github/dependabot.yml

Updated dependency

No response

What you expected to see, versus what you actually saw

• Actual Behaviour: https://github.com/YigtyORG/TakymLib/pull/207/files
  • It seems like the whole file changed.
  • A part of the diff: (actual diff shows whole file changed)

    -    steps:
    -    - uses: actions/checkout@v3
    -      with:
    -        submodules: recursive
    +    steps:
    +    - uses: actions/checkout@v4
    +      with:
    +        submodules: recursive

  • Also, this behavior makes conflicts occur when merging in the local repository.
  • When I merged Dependabot PR on the web, in the local repository, the git command recognized the file concerned as changed even if the file has no change, and I cannot discard those "no change" changes.
• Expected Behaviour
  • Diff should show only changed lines:

        steps:
    -    - uses: actions/checkout@v3
    +    - uses: actions/checkout@v4
          with:
            submodules: recursive

  • Also, conflicts should not occur on lines where nothing has changed.

Native package manager behavior

No response

Images of the diff or a link to the PR, issue, or logs

• Bump actions/setup-dotnet from 3 to 4 YigtyORG/TakymLib#204
• Bump actions/upload-artifact from 3.1.0 to 4.3.2 YigtyORG/TakymLib#205
• Bump actions/checkout from 3 to 4 YigtyORG/TakymLib#207
• Bump github/codeql-action from 2 to 3 YigtyORG/TakymLib#208
• Bump NuGet/setup-nuget from 1.1.1 to 2.0.0 YigtyORG/TakymLib#206 - sometimes working correctly

Smallest manifest that reproduces the issue

No response