onepub-dev / onepub-dev/reVault
Create git hub actions to do a release.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 1
Description
We need to decide if we do simultaneous releases or just identify which crates have changed and do a new release.
Special attention needs to be given to migration crates and language bindings.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or workflow entry points are named. First review the repository's crate layout and any existing GitHub Actions workflows, then resolve whether releases are simultaneous or limited to changed crates, including migration crates and language bindings; done means the release policy and automation scope are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100