Support » Plugin: Advanced Cron Manager - debug & control » .gitignore & composer

  • Hi,

    First i would like to say that i really like your plugin 🙂
    During the last update i noticed you made major changes moving to composer and autoload.
    But, since you add a gitignore for vendors (understandable) i had issue with versioned project of mine. Since deployement didn’t embark vendors, the plugin was unable to work.
    I know i should not add plugins to my own git but do you think keeping your .gitignore is logical / good practice ?

    Benoit.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Kuba Mikita

    (@kubitomakita)

    Hi,

    I think it is good practice. It only affects my plugin dir, so this shouldn’t be a problem.

    I don’t want to push the vendor dir to GitHub repository because it’s quite heavy.

    I’d like to help you but I can see only a resolution in your project – to handle the plugins differently (ie. via wp-cli script) 🙂

    Plugin Author Kuba Mikita

    (@kubitomakita)

    Hey, I just got another message from other developer with the same issue.

    Did you mean the SVN repository? Because I’ll be removing the .git* files from there.

    Hello,

    Yes, i meant the .gitignore is unecessary/annoying on the official repository 🙂

    Plugin Author Kuba Mikita

    (@kubitomakita)

    Ok! You can feel free to remove them for now, they will be removed from the official package upon the next release 🙂

    Plugin Author Kuba Mikita

    (@kubitomakita)

    An update – version 2.2.0 has been released and there are no Git files in the SVN now 🙂

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘.gitignore & composer’ is closed to new replies.