R2NorthstarTools / R2NorthstarTools/FlightCore
Add support for release-please
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I've been using the release-please action on a few of my other projects [^1] now and the workflow is quite nice.
[^1]: For example
- https://github.com/GeckoEidechse/mdbook-gitbook
- https://github.com/GeckoEidechse/mdbook-obsidian
- https://github.com/GeckoEidechse/remove-markdown-links
Need to look into adding support for this project as well.
Main issue is that release-please publishes release before build CI is done... Maybe I can tell it to publish as draft instead?
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
Start by reviewing the project's GitHub Actions workflow for build CI and the release-please action documentation. Determine how release creation should wait for or reflect build completion, and confirm the resulting release workflow behaves correctly without publishing prematurely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100