Skip to content

README - Update screenshots for WebUI #551

Closed

Description

@claudioantonio

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

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

Activity

  1. MichaelMure commented on Feb 3, 2021

    @MichaelMure
    Contributor

    Good idea!

  2. flawrist commented on Apr 9, 2021

    @flawrist

    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

  3. f8122dac91 commented on Aug 9, 2021

    @f8122dac91

    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?)

  4. github-actions commented on Jul 23, 2024

    @github-actions

    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
  5. github-actions commented on Feb 1, 2025

    @github-actions

    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.

  6. MichaelMure commented on Sep 13, 2026

    @MichaelMure
    Contributor

    Git-bug has a new webui, and the readme has new screenshot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions