openshift / openshift/client-go
releases?
Open
Nobody has claimed this yet.
lifecycle/frozen
- Dominant language
- Shell
- Stars
- 120
- Forks
- 183
- PR merge metrics
- No merged PRs in 30d
Description
I noticed you have very few tags. Wouldn't it make sense to create tags/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 reviewing issue #173 and its 11-comment discussion to understand the unresolved case for tags or GitHub releases. Define what release cadence, tag conventions, and project ownership would be needed before treating the request as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100