label-actions

How exactly is that proof? That's just replacing the usage of one library with another. You can go and see the original repo here: https://github.com/dessant/label-actions And the "copied" one here: https://github.com/hramos/label-actions I didn't look too much at the code, but at first glance it doesn't seem copied. The API might be the same or similar, but that's a different discussion, as is for taking the same name.

I've settled with giving automated feedback using a GitHub app I've built [1] that posts a predefined message and closes the issue when a label is applied. When it's hard to figure out what is being asked, or the bug report does not follow the issue template and there are no clear steps to reproduce the bug, I'll label the issue as `incomplete`, which asks the author to fill out the issue template properly, and closes the issue. I've also configured labels with messages for common questions [2] or issues that are outside the control of the project, so I can inform people without repeating the same things over and over. I agree that we should not be expected to provide support, though I find it acceptable for now to post automated messages, when it can help others. [1] https://github.com/dessant/label-actions [2] https://github.com/dessant

Ghost uses one of my GitHub apps [1][2] that I wrote in my free time after their CTO asked me to do it [3], and I wonder how would their CEO feel if I would ban them because I condemn wiping customer data in retaliation for being criticized in public. Even if they decide to fire a customer, they should have notified them and let them export their data. Harming your customer's business because they criticized you is likely illegal, no matter how twisted your terms of service are, and I hope they will get sued for what they've done. [1] https://github.com/dessant/label-actions [2] https://github.com/TryGhost/Ghost/blob/master/.github/label-... [3] https://github.com/dessant/support-requests/issues/6