mlabs-haskell / mlabs-haskell/lambda-buffers
Rust crate publishing and versioning
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 32
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Publish lbr-prelude and lbr-prelude-derive to crates.io
TODO
- bump version to v1
- configure CI to publish crates to crates.io on tag push
- if not to difficult, generate documentation to github pages (otherwise, using docs.rs is also sufficient)
- push a git tag
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the manifests for lbr-prelude and lbr-prelude-derive and the repository's CI configuration, then verify the crates.io and GitHub Pages or docs.rs publishing paths. Done means both crates are versioned v1, CI publishes on tag push, documentation has an agreed hosting path, and a git tag is pushed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100