I created a pull request for a small cleanup of the build requirements of GRHydro.
(1) Was anybody notified about this new pull request? (2) Can (should?) this be integrated with TRAC? Or should we switch to using Bitbucket's issue tracker? (3) Could someone have a look and then "push the button"? I'm curious what happens.
-erik
Hi,
On Thu, Oct 02, 2014 at 03:31:19PM -0400, Erik Schnetter wrote:
I created a pull request for a small cleanup of the build requirements of GRHydro.
Thanks.
(1) Was anybody notified about this new pull request?
I didn't receive anything.
(2) Can (should?) this be integrated with TRAC? Or should we switch to using Bitbucket's issue tracker?
I am not sure about the first part, but we now have so many tickets in trac that I would refrain from switching. I am also not sure how well this would work with components that are not in bitbucket (but I would assume that this should be possible).
(3) Could someone have a look and then "push the button"? I'm curious what happens.
- There is no pull request in 'my list' on bitbucket. - At the moment I have to go find it within the EinsteinEvolve repository (I have to know that there is one first).
I commented on bitbucket on the changes.
Frank
On 2 Oct 2014, at 12:31, Erik Schnetter schnetter@cct.lsu.edu wrote:
I created a pull request for a small cleanup of the build requirements of GRHydro.
(1) Was anybody notified about this new pull request?
Not unless they asked to be. If you want to be notified about things that happen to a repository, you need to subscribe to those changes by "watching" the repository. This is done through the little "eye" icon in the top right of the repository overview page (https://bitbucket.org/einsteintoolkit/einsteinevolve/overview). You can watch pull requests, commits or forks. You would have to do this for each repository, which is clearly not convenient for us, since we are a project with many repositories.
The functionality to have pull requests sent to an email list is not implemented (https://bitbucket.org/site/master/issue/10279/provide-pull-request-email-hoo...). You can instead set up a hook to POST to a URL on each pull request. We would need to provide such a URL which sent the information to the mailing list. Maybe Frank, or someone with some PHP enthusiasm could set up such a service?
Alternatively, one person could watch all the repositories (potentially via a script), and set up an email filter to forward the notifications to the list. I prefer the POST hook approach (which would also probably be set up using a script) as it doesn't rely on a single person's email account.
(2) Can (should?) this be integrated with TRAC? Or should we switch to using Bitbucket's issue tracker?
I think it's more important that we have all the issues in one place, than to have integration with bitbucket. I don't know how well set up bitbucket is for projects with so many repositories, and its issue tracker is fairly rudimentary. We probably need to do the gluing ourselves, as there doesn't seem to be anything currently available. As a framework, encompassing various repository types, hosted in various places etc, it's unlikely that we find a nice out-of-the-box integrated solution. If we had a single repository, things would be a lot simpler, but then we wouldn't have a framework, we would just have a code.
users@lists.einsteintoolkit.org
-
Erik Schnetter -
Frank Loeffler -
Ian Hinder