Cello CICD
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go, kubernetes
- Domain
- ci-cd, networking, testing-qa
Research direction
No files or entry points are named. Start by reviewing issue #4 and the repository's CI and test layout; done means the NetworkPolicy and E2E test checklist items are completed.
Written by the indexing model from the issue text.
Description
CICD todos:
- #4
- NetworkPolicy Test
- E2E test
- Dominant language
- Go
- Stars
- 104
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from volcengine/cello
-
Conformance TestOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
volcengine/cello#4 ·
All issues in volcengine/cello
Similar issues
-
raised-by:worker
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
medici-finance/assay#2486 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openimsdk/openim-sdk-core#1127 ·
-
github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Hochfrequenz/aibap.mcp#578 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mvanhorn/cli-printing-press#4980 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
lenaxia/LLMSafeSpaces#1644 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day