typelevel / typelevel/typelevel.g8

Notes from live demo

Open
#106 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
14
Forks
7
Avg merge
5d 16h
Merged PRs (30d)
3

Description

  • Perhaps add instructions about needing to git init and create a commit
  • Can we pull name info from git config?

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

No files or tests are named; start by locating the setup instructions and the git-related template behavior in the repository. Done means the required git init and commit steps are documented and the expected use of git config for the name is clarified or implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, scala
Domain
developer-experience
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.