axodotdev / axodotdev/oranda

Custom releaser

Open
#687 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
543
Forks
34
PR merge metrics
No merged PRs in 30d

Description

Hello!
I would like to use oranda with other programming languages / actions.
I don't mind parsing myself and provide the final manifest to oranda.
But I'm not sure what exactly and how oranda can work in such a way.

For instance, I have the project [thewh1teagle/gcb](https://github.com/thewh1teagle/gcb)
And I would like to add oranda manually (I don't want to wait until oranda officially supports goreleaser)
I can write the logic myself to parse the releases and getting URLs + name of assets.
Plus - writing manually the project title, description etc - all the things which are parsed from `Cargo.toml`
But then how do I pass all that information to oranda?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how oranda currently reads Cargo.toml and constructs its release manifest. Identify the entry point or input contract needed for externally supplied project metadata, release URLs, asset names, and descriptions, then define how a custom releaser such as gcb could provide them and how that flow would be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.