Hi, I recently ran into this while I was looking to finally fork the underlying yuicompressor project in order to keep it alive. I see that you’ve since done that as well, and also replaced the Maven plugin.
Could you help me understand why my fork wasn’t considered as a candidate for switching to a modernized version of yuicompressor?
My fork is here:
https://github.com/hazendaz/yuicompressor-maven-plugin
It may be because my repository no longer appears in the fork network. I intentionally disconnected it some time ago, as I had no intention of continuing upstream given that the original project was retired and my fork had accumulated a significant number of commits beyond it. I’ve done this in similar situations when reaching major milestones, since otherwise self–pull requests would continue to surface in the upstream network even when there was no realistic path forward.
Because I didn’t submit a GitHub request to retain the original fork relationship—which I felt was unnecessary—the repository simply left the fork network. In hindsight, I probably should have noted that more clearly upstream.
Beyond this question, are there any considerations I should be aware of if I incorporate your updated yuicompressor into my fork moving forward?
Hi, I recently ran into this while I was looking to finally fork the underlying yuicompressor project in order to keep it alive. I see that you’ve since done that as well, and also replaced the Maven plugin.
Could you help me understand why my fork wasn’t considered as a candidate for switching to a modernized version of yuicompressor?
My fork is here:
https://github.com/hazendaz/yuicompressor-maven-plugin
It may be because my repository no longer appears in the fork network. I intentionally disconnected it some time ago, as I had no intention of continuing upstream given that the original project was retired and my fork had accumulated a significant number of commits beyond it. I’ve done this in similar situations when reaching major milestones, since otherwise self–pull requests would continue to surface in the upstream network even when there was no realistic path forward.
Because I didn’t submit a GitHub request to retain the original fork relationship—which I felt was unnecessary—the repository simply left the fork network. In hindsight, I probably should have noted that more clearly upstream.
Beyond this question, are there any considerations I should be aware of if I incorporate your updated yuicompressor into my fork moving forward?