sindresorhus/caprine

Transition fork users to official Caprine after new version

Open

#1,875 opened on Aug 7, 2022

View on GitHub
 (10 comments) (0 reactions) (0 assignees)TypeScript (7,365 stars) (601 forks)user submission
help wantedquestion

Description

I'm not sure about how to transition users of lefterisgar/caprine to upstream when the new release comes out. Maybe create a transitional release on my fork and change the repo to sindresorhus/caprine? Is that good enough or is there any better way?

Contributor guide

Tech stack
None
Domain
release
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Understanding of GitHub fork workflow
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue discusses how to transition users of a fork to the upstream Caprine after a new release. Review the comments for suggestions, such as creating a transitional release on the fork and redirecting to the main repo. The maintainer may need to clarify the preferred approach. No code changes are required; this is a community management task.
Transition fork users to official Caprine after new version · sindresorhus/caprine#1875 | Good First Issue