[stub] automatically make a pre-release based on main
Open
Nobody has claimed this yet.
enhancement
priority/undecided
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
To make it easier to test out the latest bleeding edge code, every merge to main should update a pre-release that could used like so:
kubectl apply -f https://get.pinniped.dev/main/install-pinniped-concierge.yaml
This would of course be an unsupported build.
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 with the requested merge-to-main flow and the kubectl command using https://get.pinniped.dev/main/install-pinniped-concierge.yaml. Determine how a pre-release should be updated after each merge and verify that the URL serves the resulting unsupported build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100