livebud / livebud/weblog

Feedback: initial confusion about the purpose of this repo

Open
#4 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Description

It seems that this is a sort of next branch for the code that will get templatized into bud in future releases. This wasn't completely clear to me initially from wherever I found the link to this repo, and I was looking at this as a sort of example/template repo for how to use the currently-released version.

Is there a good example repo that I can study that uses the currently released version?

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

Review the repository description and existing landing-page documentation first; the issue says the repo’s relationship to Bud and its intended use were unclear. Done means clearly identifying this as a future templatized branch and providing a pointer to an example using the currently released version.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.