Embedded git repository warning

  • Resolved brees

    (@brees)


    6 years, 7 months ago

    Hello,

    Our WordPress site’s version control is managed with git. When I download the plugin and manually install, I get some warnings about adding embedded git repositories. Can I safely ignore these warnings? How should I handle them? This is the entirety of the response in the terminal:

    warning: adding embedded git repository: wp-content/plugins/object-sync-for-salesforce/vendor/a5hleyrich/wp-background-processing
    hint: You’ve added another git repository inside your current repository.
    hint: Clones of the outer repository will not contain the contents of
    hint: the embedded repository and will not know how to obtain it.
    hint: If you meant to add a submodule, use:
    hint:
    hint: git submodule add <url> wp-content/plugins/object-sync-for-salesforce/vendor/a5hleyrich/wp-background-processing
    hint:
    hint: If you added this path by mistake, you can remove it from the
    hint: index with:
    hint:
    hint: git rm –cached wp-content/plugins/object-sync-for-salesforce/vendor/a5hleyrich/wp-background-processing
    hint:
    hint: See “git help submodule” for more information.
    warning: adding embedded git repository: wp-content/plugins/object-sync-for-salesforce/vendor/developerforce/force.com-toolkit-for-php
    warning: adding embedded git repository: wp-content/plugins/object-sync-for-salesforce/vendor/pippinsplugins/wp-logging

    I’m sorry – I searched and couldn’t find any reference to this.

    Thank you,
    Brandon

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Jonathan Stegall

    (@jonathanstegall)

    Hm, I haven’t seen that message myself. I’m inclined to think it is not a problem, but rather that we need to make sure the .git folders from the vendor libraries are not included in the plugin.

    But before I say you can safely ignore it, can you verify that the following files exist?

    1. /wp-content/plugins/object-sync-for-salesforce/vendor/pippinsplugins/wp-logging/WP_Logging.php
    2. /wp-content/plugins/object-sync-for-salesforce/vendor/a5leyrich/wp-background-processing/wp-background-processing.php

    If so, I think you should be okay to ignore, but this is a thing I’ll try to address in our next release.

    Thread Starter brees

    (@brees)

    Wow, you are fast!

    After manually dropping the folder in /wp-content/plugins/ and running git add ., I see these in the output (niether of which have the .php extension, while other added files do):

    new file: wp-content/plugins/object-sync-for-salesforce/vendor/a5hleyrich/wp-background-processing
    new file: wp-content/plugins/object-sync-for-salesforce/vendor/pippinsplugins/wp-logging

    Here’s what git won’t stage:

    modified: wp-content/plugins/object-sync-for-salesforce/vendor/developerforce/force.com-toolkit-for-php (modified content)

    Thread Starter brees

    (@brees)

    I can probably just remove the .gitignore files from the vendor directories, yes?

    Plugin Author Jonathan Stegall

    (@jonathanstegall)

    Yes, I think you’re right. I’ve updated the plugin directory’s repo to reflect this as well, although I haven’t flagged it as a new version.

    But try that and see if it works. I think it will. I haven’t had to do this myself but it makes sense that this would be an issue for some configurations.

    Thread Starter brees

    (@brees)

    Hmm. Git won’t stage these, even after removing all of the .gitignore files:

    modified: wp-content/plugins/object-sync-for-salesforce/vendor/a5hleyrich/wp-background-processing (modified content, untracked content)
    modified: wp-content/plugins/object-sync-for-salesforce/vendor/developerforce/force.com-toolkit-for-php (modified content, untracked content)

    If these don’t get committed am I going to run into issues? Feels like I will.

    Plugin Author Jonathan Stegall

    (@jonathanstegall)

    Yes, if the files from those directories are missing, there’ll be issues. I’m no Git expert, so I’m a bit out of my league there. But here are some things I’m inclined to think you could try:

    1. Re install the plugin from the WP repository and see if you can do kind of a reset. Perhaps it has been confused by the unnecessary git files and a fresh install would fix that?
    2. Install the plugin from GitHub. I hope you don’t have to do that, unless you prefer doing that, but it does have a repository at https://github.com/MinnPost/object-sync-for-salesforce.

    Thread Starter brees

    (@brees)

    Let me give those a shot. Thank you so much for all the help.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Embedded git repository warning’ is closed to new replies.