Skip to content

patronize users for using shared folders for repos #27

Description

@thirschbuechler

I've used a git repo (with remotes) analysis script in a shared dropbox folder, where also large measurement data resides.

This is a bad idea, and causes git (and git submodule assistant) to freak out. I didn't know any better and all the things that can go wrong.

I'd suggest looking for this behavior and advising against it (similar to "do you really want to be on the master branch")

  • same git submodule added multiple times in .gitmodules and shown multiple times in vscode
  • .git/index.lock': File exists. Error
  • can't find commit "null " (due to aborted submodule commit i guess) - see image
  • can't find commit xyzabcd (though commit xyzabcde is existant" - see image

I've used a git repo (with remotes) in a shared dropbox folder, where also large msr files reside.

This is a bad idea, and causes git (and git submodule assistant) to freak out.

I'd suggest looking for this behavior and advising against it (similar to "do you really want to be on the master branch")

  • same git submodule added multiple times in .gitmodules and shown multiple times in vscode
  • .git/index.lock': File exists. Error
  • can't find commit "null " (due to aborted submodule commit i guess) - see image
  • can't find commit xyzabcd (though commit xyzabcde is existant" - see image

no_banch_null

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