Hi Ron,

I don't believe Git offers a way to force post-commit hooks to be installed
in clones of a repository (likely for security reasons). They have a
concept called "templates" which can auto-populate content in a cloned Git
repository, but I don't think the repository you clone can control the
templates. I think each person cloning would have to set it up
individually. You may have to control all this in-house by making it part
of the development and checkout process run by your engineers. Perhaps some
sort of custom clone script, or a script that's run when people first set
up a build from their cloned repository. It's outside the scope of Review
Board, and not something we can help too much with.

If you wanted to run something when pushing to a repository, you'd have to
write a small web service/script that GitHub can HTTP POST to. They have
documentation on how to do that, but Review Board has nothing that's going
to be able to help you here, as it's a bit outside the scope and would be a
custom in-house workflow.

Christian

On Tue, Oct 1, 2019 at 11:10 AM Ron T <[email protected]> wrote:

> Christian,
> When a user commits or pushes from a GUI editor to their local repository
> which is a clone of their github repository, how do I get reviewboard to
> send out a notification? In this case they are not running the rbt post
> command because they are using a GUI.
>
> I see that each local repository has a ./git/hooks directory.  Does a hook
> have to be written in that directory to be triggered on commit and/or push?
> If so can the .git/hooks directory be accessed on github so a post-commit
> hook could be added for this purpose?  This way it would be accessible for
> anyone that clones the repository. Or is there a better way of doing this
> such as using a .reviewboardrc file?
>
> Thanks.
>
> On Tue, Sep 24, 2019 at 2:51 AM Christian Hammond <
> [email protected]> wrote:
>
>> Hi Ron,
>>
>> The built-in WebHook support for GitHub is used to automatically close
>> review requests when a commit referencing the review request ID is pushed
>> to the repository. It's an incoming WebHook that GitHub can send to
>> (providing GitHub has the ability to reach your server), but it's not
>> designed for custom uses.
>>
>> It sounds like what you're looking to do is to have people post code for
>> review by committing to the repository first? If so, that's what's
>> generally referred to as a post-commit model, where the code is already in
>> the codebase and is then going through review. A pre-commit model, where
>> you post to Review Board first and only push to the repository after going
>> through a successful review cycle, is recommended to ensure nothing slips
>> through the cracks or ends up in the repository without approval.
>>
>> If you're needing some sort of custom e-mails to be sent out when
>> activity happens on your GitHub repository, then that's going to require
>> custom work. You'd need something (whether an independent script of your
>> own creation written in your language of choice, or an extension to Review
>> Board written in Python) that GitHub can HTTP POST to, and then you'd need
>> to configure a new WebHook entry in GitHub to point to that. Your script
>> could take that commit and post it for review, or e-mail people, or
>> whatever you'd prefer.
>>
>> Review Board already does send out e-mails to any reviewers (individual
>> people or configured review groups) whenever there's a new review or reply
>> on a review request. Is there a different type of notice you're looking
>> for, like making a comment on the commit on GitHub? If so, your custom
>> script/extension would do that.
>>
>> Christian
>>
>>
>>
>> On Thu, Sep 19, 2019 at 3:26 PM Ron A <[email protected]> wrote:
>>
>>> Hi, I have repository setup at github and it's linked to reviewboard 3.0
>>> and I receive a 200 OK response.
>>> The reviewboard server is on premise.
>>>
>>> I have followed the directions here
>>> https://www.reviewboard.org/docs/manual/3.0/admin/configuration/repositories/github/
>>> which seem to indicate once the webhook is inserted in the github
>>> repostiory everything will work. The instructions don't seem to be complete.
>>> "Then click *Add webhook*. You're done!"
>>>
>>> I would like to have reviewboard send out a review request with a link
>>> to a diff when a person has made a commit to the github repository.
>>> I would also like to have reviewboard send out a notice when someone has
>>> reviewed a commit on reviewboard.
>>> Is there a directory where a github webhook is located on the
>>> reviewboard server?
>>> Does the mydomain.com url below need to reference the webhook by name?
>>>
>>> The payload url is this according to the instructions.
>>> https://mydomain.com/reviewboard/repos/3/github/hooks/close-submitted/
>>>
>>> Instructions say to include the information below when closing a commit.
>>> Review Request #123
>>>
>>> I make a commit and push it to github but don't receive any notification.
>>> Thanks, Ron
>>>
>>>
>>>
>>> --
>>> Supercharge your Review Board with Power Pack:
>>> https://www.reviewboard.org/powerpack/
>>> Want us to host Review Board for you? Check out RBCommons:
>>> https://rbcommons.com/
>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Review Board Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/reviewboard/8c138fc3-9245-4867-8018-71862cef088e%40googlegroups.com
>>> <https://groups.google.com/d/msgid/reviewboard/8c138fc3-9245-4867-8018-71862cef088e%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> --
>> Christian Hammond
>> President/CEO of Beanbag <https://www.beanbaginc.com/>
>> Makers of Review Board <https://www.reviewboard.org/>
>>
>> --
>> Supercharge your Review Board with Power Pack:
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons:
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Review Board Community" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/reviewboard/HNAm-l2vxLQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/reviewboard/CAE7Vndmftas22Y4hVm8-B-y9SP0G6pvxDwC0eYuu1YBkeL27Wg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/reviewboard/CAE7Vndmftas22Y4hVm8-B-y9SP0G6pvxDwC0eYuu1YBkeL27Wg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/reviewboard/CAKTzQdVo4TgOJ_AvS2E3rsfo3nqe_UyC97YSM%3DExHYQbcVMVVw%40mail.gmail.com
> <https://groups.google.com/d/msgid/reviewboard/CAKTzQdVo4TgOJ_AvS2E3rsfo3nqe_UyC97YSM%3DExHYQbcVMVVw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Christian Hammond
President/CEO of Beanbag <https://www.beanbaginc.com/>
Makers of Review Board <https://www.reviewboard.org/>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CAE7VndmLC7RBn41-Qtuxy%2BLE6aBZekcpvb-rHvLE5tKhA06Q7Q%40mail.gmail.com.

Reply via email to