obophenotype / obophenotype/ncbitaxon

Plan on regular (scripted?) releases?

Open
#13 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
31
Forks
7
PR merge metrics
No merged PRs in 30d

Description

Is there any plan/idea/need to get this updated on a regular basis?

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the repository's current build and release process, then read the issue discussion for existing requirements and constraints. Define what regular scripted releases would need to automate and how a successful release cadence would be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.