• 3 Posts
  • 78 Comments
Joined 8 months ago
cake
Cake day: May 6th, 2024

help-circle

  • Give it to the dev, and explain the situation. Let them know it seems too big/complex of a PR, but you’re willing to make additional changes, or break up PR to make it more palatable for merging. It’s in the dev’s hands after that.

    I don’t think you should release your own fork without at least trying to work with the original project.

    Make sure all your commits have detailed commit messages so that the dev can follow what you were doing (upgrading deps, refactor because xyz, etc.) Don’t just record what was changed, explain why it was changed.

    anyway that’s what I would do.















  • Cool assumption bro. Hope that works out for you.
    I am never rude to the poor people that have to work retail. I know the pain; I have been on the other side of the counter.

    What I’m talking about is malicious compliance.

    They tell the cashiers to push the program and be helpful? Fine. I will let that cashier be the most helpful employee ever and at the same time gum up the company data collection system with fake information.

    At the same time as more punshment to the company they will see reduced sales and throughput requiring additional cashiers (more hours/pay for those people).

    But please bring on the fake internet point brigade.