spring-cloud / spring-cloud/spring-cloud-github-actions
K8S and Vault Need Custom ci-release.yml
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 6
Description
When creating a new -internal and release branch for k8s and vault they need a custom ci-release.yml.
See https://github.com/spring-cloud/spring-cloud-vault-commercial/commit/8f12b47676ef4a3949c1679a7d3c9b5dfcff5ef0
https://github.com/spring-cloud/spring-cloud-kubernetes-commercial/commit/dcbbfcc8df1139117837ba18db9418fc38b06350
https://github.com/spring-cloud/spring-cloud-kubernetes-commercial/commit/bdbd473ac3f30fbe4d80f97acfd309f24cc9dc87
https://github.com/spring-cloud/spring-cloud-kubernetes-commercial/commit/f22a0cbff3283338149aba8a2a1e84ef98f5c45d
https://github.com/spring-cloud/spring-cloud-kubernetes-commercial/commit/e617fc105579b982f209921730a8293753710637
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 referenced spring-cloud-vault-commercial and spring-cloud-kubernetes-commercial commits, focusing on their custom ci-release.yml changes. Apply the corresponding workflow configuration for new -internal and release branches for Kubernetes and Vault, then verify the resulting branch release behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100