• This is any specific reason why the vendor/ directory is being gitignored? This causes fatal issues on sys that relay on GIT actions.

    If there’s not a reason for this behavior, I would recommend removing line 7 from the root .gitignore file.

Viewing 1 replies (of 1 total)
  • Plugin Author Boone Gorges

    (@boonebgorges)

    The /vendor/ directory contains files that are pulled into the project as part of a Composer build step. As such, we don’t track these files during plugin development. Removing the line from .gitignore is not an option for this reason.

    The .gitignore file is intended for plugin development, and is unneeded in the package distributed on wordpress.org. I’ve changed the svn props on the wordpress.org repo so that the .gitignore file is ignored. It will not be part of the next release.

    I’m unsure what kind of system behavior would require you to look at the .gitignore files inside of WordPress plugin directories. Perhaps you are pulling from GitHub instead of from wordpress.org? If so, then you need to add full-fledged build steps (npm run build, composer install, etc) into your system tools. Anyway, it’s probably safe to delete the file wp-content/plugins/buddypress-group-email-subscription/.gitignore while you await the next plugin update.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.