Skip to content

Move operation hardcodes mode, drops executable permission #25

Description

@cmanallen

The MoveCommitAction handler in the GitHub provider hardcodes mode="100644" for the new file's tree entry. If the original file was executable (100755), the move silently drops the executable permission. The get_file_content call retrieves the blob SHA but not the file mode, and unlike GitLab's native move action (which preserves mode automatically), the GitHub emulation always resets to 100644.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions