

With both Gitea and Forgejo, sometimes you need to hardcode the action URL, like:
https://github.com/actions/setup-java@v4
With both Gitea and Forgejo, sometimes you need to hardcode the action URL, like:
https://github.com/actions/setup-java@v4
I agree. I love seeing community engagement when there’s an actual question involved.
My issue is with the flood of incredibly, incredibly basic questions being repeated over and over again. Especially when the user isn’t even looking for discussion - just an answer. Essentially treating the community like their own human-powered search engine. Gives off the vibe that they OP’s don’t care enough to put any effort in, they just want someone else to spoon-feed them and/or tell them what to do. Seems so mindless.
And, the sheer volume of posts that fit that description can, and do, inadvertently drown out the less frequent, but more valid questions and requests for help… which just, sucks.
I see where you’re coming from. “Any publicity is good publicity”, as they say. So, sure… traction is good for overall visibility. I agree. We do need more of that.
To counter your counter, for the sake of discussion:
If the traction is built on semi-incoherent noise, doesn’t that feel precarious? Artificial, even? Kinda reminds me of bot-boosting, where you’d see a big initial uptick in views and maybe drum up some actual buzz. But in the long term, it’s either a fart in the wind, or it backfires altogether and ends up fueling a negative public opinion.
Yeah, figured it was a bit of a coin toss. Eye of the beholder, and all that. I did rewrite the post a few times to dial back my spiciness… maybe it would have been a better fit if I left it sounding extra bitchy 🤣
Well, yeah, thats why I’m saying if the action isn’t available directly from Forgejo, just write out the full action URL like the example in my last comment and pull it directly from GitHub. Most/all of the actions you’re pulling from Forgejo are originally forked from GitHub anyway. ¯\_(ツ)_/¯