You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
webui --read-only does not show any bugs on my test build. But without this flag I see all bugs and can create new bugs as well.
Steps to reproduce:
clone git-bug
build the latest version
git-bug version shows
git-bug undefined 9427c45 go1.25.1 X:nodwarf5 linux amd64
git-bug pull
The following command shows all bugs the termui shows I can even enter new bugs with firefox
git-bug webui --no-open --log-errors -p 40053
The following command shows no bugs at all
git-bug webui --no-open --log-errors -p 40053 --read-only
Is this the expected behaviour? If true it would be nice to have an option for anonymous view?
Why I would like to see all bugs as anonymous user?
My current plan is to use git-bug webui to show bugs on each of my cgit repository listings.
Then I want to allow anonymous users to send a email with the bug id to reply on the bug or create new bugs. Then having a daemon on my server which has access to my git repository and create the user from the email header remove all non alphanumeric characters and check with a bad words list. Then the daemon would use git-bug to enter the bug or add the comment. This would also allow to use mailing lists to comment on bugs or create bugs. Sort of what patchwork is for "pull requests"
Second I want to set up a simple web form to do the same thing.
Another idea I might be able to come up with is a set of git hooks with a of a proof of work mechanism which also restricts the access to only ref/bugs but I need to do more research on this one.
webui --read-only does not show any bugs on my test build. But without this flag I see all bugs and can create new bugs as well.
...
Is this the expected behaviour? If true it would be nice to have an option for anonymous view?
no, this is not the expected behavior, but it is a known bug: #1433
because this is what this issue was opened for, i'm going to close this as a duplicate, but i will adress your other comments below.
My current plan is to use git-bug webui to show bugs on each of my cgit repository listings.
This and the expanded description you provide aligns well with our vision for git-bug -- namely, that something like --read-only should work to display a read-only mode of the issues and comments that git-bug knows about, and to expand on this, support authentication so that external users and contributors can sign in and mutate data as well (e.g. create issues, add comments).
If you'd like to help contribute to git-bug by working in this area, we'd welcome the assistance. Feel free to join us on matrix and we can chat more.
Activity
sudoforge commentedon Sep 26, 2025
no, this is not the expected behavior, but it is a known bug: #1433
because this is what this issue was opened for, i'm going to close this as a duplicate, but i will adress your other comments below.
This and the expanded description you provide aligns well with our vision for git-bug -- namely, that something like
--read-onlyshould work to display a read-only mode of the issues and comments that git-bug knows about, and to expand on this, support authentication so that external users and contributors can sign in and mutate data as well (e.g. create issues, add comments).If you'd like to help contribute to git-bug by working in this area, we'd welcome the assistance. Feel free to join us on matrix and we can chat more.