Maybe just one animated gif presenting a simple use case like:

1. create an issue
2. add comment to issue
3. close issue

Good idea!

README lacks a quick start guide, because any command you pass to git-hub.exe ends with the error so far Error: git-bug must be run from within a git repo

I recently returned to this project after a couple of years. It's great to see it progresses, but it still feels like the project is lacking documentation targeting users. A getting started document with some ideas on the workflow for using git-bug in a real development scenario would be a great addition to the project.

@sergeevabc sounds like your current directory is not a git-repo. Are you sure you are issuing the command within a git repo? If you just cloned a repo and was issuing the command, you have to change your directory into the repo you just cloned. (also do you mean git-bug.exe?)

Michael Muré (MichaelMure) added label help wanted 3 years ago

Michael Muré (MichaelMure) added label Easy pick 3 years ago

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 1 year ago

sudoforge removed label Easy pick 1 year ago

sudoforge removed label help wanted 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten 10 months ago

github-actions (github-actions) removed label lifecycle/stale 10 months ago

sudoforge removed label lifecycle/dormant 7 months ago