Move releases from GitHub Actions to Drone CI about drone-cache HOT 4 CLOSED

@bdebyl I looked at the output in an incognito browser window, and yes, I can see it.
Excellent, so meltwater org membership isn't required for that.

Thanks for exploring this with me :)

from drone-cache.

@bdebyl would open source contributors have access to build information in Drone as well?
Similar to what they can see in the GitHub Actions output today?

from drone-cache.

@spier are you able to see the Drone CI build outputs from the commits here? If so then yes.

The only step that's used by GitHub Actions is Goreleaser, which I assume was used with Actions as it has more straightforward release creation than what one might see in Drone CI for GitHub.

Beyond that I don't see any advantage in maintaining two separate CI platforms.

from drone-cache.

Seems like GITHUB_TOKEN is an automatically generated and managed secret as part of Action workflows.

Read more here

This means that Action workflows are unique in not requiring explicit secrets for generating a release and can use the natively baked in ones. So far I have been unable to find anything in Drone CI that does something similar, and a manually token would need to be generated which is not ideal.

Closing this due to the handy and secure functionality that GitHub Actions allows vs. lack of such functionality from Drone CI. Will re-open if Drone adds support for something like this with the GitHub plugin.

from drone-cache.