Open kip93 opened 1 year ago
Hey @kip93, sorry for the delay. I remember seeing this, but I was traveling at the time.
You're right that GitHub is the only way to publish. It is some relatively straightforward curl commands against the GitHub an FlakeHub API to publish, but unfortunately it isn't so simple: we use the GitHub JWT to validate if publishing is permitted.
Our roadmap does include support for other forges (and local CLI pushing) but it isn't in the super near term yet. Can you describe your use case? I'll add it to the board to help with scheduling.
It's not much of a "use case" rather than it would just be adding another CI to a project that is not mainly hosted on github for the single purpose of publishing it to flakehub. Though I do set up mirrors to github for these type of projects anyway, so it's just a matter of adding the github action and let the mirroring do it's thing; it's just me of not wanting to split things into different places when I don't need to.
That said, maybe this can be worked around for now by creating a github token and putting it as a secret on any other CI one uses, so it's urgency might not need to be too high.
Are there any plans to be able to use non-github flakes? Currently it seems like the only way to push is using this github action. It seems to use curl commands to some URLs, maybe these can be documented somewhere?