Re: setup issues (remote git/cgit)

2024-08-09 Thread Bagels1b
Can the Raw File URL Mask reference any file in the repository or should it be something specific? On Monday, August 5, 2024 at 1:12:50 PM UTC-4 Bagels1b wrote: > I'm trying to get my first ReviewBoard server (7.0.1) up and running but > I've run into a number of issues. My RB is on Ubuntu 22.

"New Review Request" repo info missing

2024-08-09 Thread Bagels1b
This is a new 7.0.1 ReviewBoard setup using a remote Git repository. It's mostly up and running. I've added the remote Git repository and I can use 'rbt post' to create a Draft Review. Then I can edit and publish it using the web gui or rbt. However if I navigate to the "New Review Request"

Re: setup issues (remote git/cgit)

2024-08-09 Thread David Trowbridge
The raw file mask is essentially a format string, which the server uses to create the URL to fetch blob content. It should explicitly have "" and "" in it, not a specific file or revision. So for your case, it should be "http://myserverurl/cgit/myrepo/blob/ ?id=" David On Fri, Aug 9, 2024 at 6:0

Re: "New Review Request" repo info missing

2024-08-09 Thread David Trowbridge
The post-commit (post-push) UI is only implemented for certain hosting services where we have both the APIs we need and the demand from users to implement it. For the vast majority of cases, our workflow recommendation is to use rbtools to review code before it gets landed into a central repository

Re: setup issues (remote git/cgit)

2024-08-09 Thread Bagels1b
Thanks David! That solved two issues I was having. Documenting them below to hopefully help someone else out in the future. Doing 'rbt post' for some file modifications resulted in "The patch to didn't apply cleanly". After fixing the "Raw File URL Mask" this problem has gone away. My 2nd

Re: "New Review Request" repo info missing

2024-08-09 Thread Bagels1b
Thanks for letting me know David. On Friday, August 9, 2024 at 12:38:35 PM UTC-4 David Trowbridge wrote: > The post-commit (post-push) UI is only implemented for certain hosting > services where we have both the APIs we need and the demand from users to > implement it. For the vast majority of