python-packaging / python-packaging/skel

regen-git should care about upstream/skel

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

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
2
Avg merge
48m
Merged PRs (30d)
1

Description

  1. when upstream/skel exists but skel does not
  2. when skel is behind upstream/skel

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.

Research direction

Start by locating the regen-git entry point and reading how it handles skel and upstream/skel. Reproduce the two listed cases—when upstream/skel exists without skel, and when skel is behind it—then confirm the intended behavior and add coverage for both cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.