luckyframework/lucky_cli

Provide lucky init --edge support

Open

#744 opened on Mar 20, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (49 forks)auto 404
feature requesthacktoberfest

Repository metrics

Stars
 (92 stars)
PR merge metrics
 (PR metrics pending)

Description

One of the woes of installing lucky_cli from source is that, in order for lucky init to work properly, you must be on a tag.

I would be nice if the functionality of lucky init worked as such:

  • lucky init always yields an app checked out from $LATEST_TAG of all respective repos
  • If a user passes an --edge flag, lucky init uses branch: main for all lucky deps

We might be able to look to rails for how to achieve this.

One way this might work better too, is to have the "concerns" of app gen be inside lucky/another repo, and have the "lucky cli" functions in this repo, then clone via linked tag/edge from there.

Lots of ways to achieve this easily, but picking the best way for the future is important here.

Contributor guide

Research direction
Investigate how lucky init currently fetches templates and how to conditionally use main branch instead of tags. Look at Rails' approach for inspiration.
Tech stack
None
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CrystalLuckyGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75