Migrate to Prow CI

Open
#659 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes

Research direction

The issue names Prow CI and Kubernetes test deployments but no files, tests, or entry points. Start by mapping the current process that periodically pulls and recreates pods, then define the migration scope and validation for refreshed test deployments. Done means the repository uses Prow CI for this workflow without that periodic pod refresh.

Written by the indexing model from the issue text.

Description

We can migrate to Prow CI so that we do not need to periodically pull and recreate pods to refresh test deployments in k8s.

Dominant language
TypeScript
Stars
69
Forks
59
Avg merge
1d 10h
Merged PRs (30d)
26

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from goplus/builder

All issues in goplus/builder

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.