mapt-oss / mapt-oss/mapt-operator
[CI] Setup proper CI strategy based on gh actions
Open
Nobody has claimed this yet.
component/CICD
good first issue
priority/HIGH
- Dominant language
- Go
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Similar to https://github.com/mapt-oss/cloud-importer setup a strategy to build operator images and publish them to ghcr (PRs) or quay ( releases)
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 comparing the CI setup in the referenced cloud-importer repository and then inspect this repository's current build and workflow configuration. Define the workflow needed to build operator images and publish them to GHCR for pull requests and Quay for releases; done means both publication paths work as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100