You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Pranav Sharma <pr...@gmail.com> on 2016/02/12 17:58:03 UTC
Branch not visible.
I have pushed a branch on the main repository, with the new credentials
after iCLA. But the branch is not visible online.
Re: Branch not visible.
Posted by Dave Brondsema <da...@brondsema.net>.
We normally just mention the branch name, and the reviewer will check it
out locally to look at it and test.
On 02/12/2016 10:45 PM, Pranav Sharma wrote:
> Thanks for the info, but I just needed to comment a link of a commit on
> ticket page for review. Is there a way to do so?
>
> On Sat, Feb 13, 2016 at 3:11 AM, Dave Brondsema <da...@brondsema.net> wrote:
>
>> On 2/12/16 11:58 AM, Pranav Sharma wrote:
>>> I have pushed a branch on the main repository, with the new credentials
>>> after iCLA. But the branch is not visible online.
>>>
>>
>> We have a custom script on the forge-allura.apache.org server to sync the
>> official git repo (git-wip-us.apache.org) over to our allura server to
>> show up
>> in the code browser. Right now the script only notices changes on the
>> master
>> branch. (After something is updated on master it will do a pull and get
>> branches then)
>>
>> Of course it would be better to have it pick up on branch and tag changes,
>> not
>> just master, but that's how it is right now. And its not really a problem
>> for
>> development since your branches really are there.
>>
>>
>> --
>> Dave Brondsema : dave@brondsema.net
>> http://www.brondsema.net : personal
>> http://www.splike.com : programming
>> <><
>>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: Branch not visible.
Posted by Pranav Sharma <pr...@gmail.com>.
Thanks for the info, but I just needed to comment a link of a commit on
ticket page for review. Is there a way to do so?
On Sat, Feb 13, 2016 at 3:11 AM, Dave Brondsema <da...@brondsema.net> wrote:
> On 2/12/16 11:58 AM, Pranav Sharma wrote:
> > I have pushed a branch on the main repository, with the new credentials
> > after iCLA. But the branch is not visible online.
> >
>
> We have a custom script on the forge-allura.apache.org server to sync the
> official git repo (git-wip-us.apache.org) over to our allura server to
> show up
> in the code browser. Right now the script only notices changes on the
> master
> branch. (After something is updated on master it will do a pull and get
> branches then)
>
> Of course it would be better to have it pick up on branch and tag changes,
> not
> just master, but that's how it is right now. And its not really a problem
> for
> development since your branches really are there.
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
Re: Branch not visible.
Posted by Dave Brondsema <da...@brondsema.net>.
On 2/12/16 11:58 AM, Pranav Sharma wrote:
> I have pushed a branch on the main repository, with the new credentials
> after iCLA. But the branch is not visible online.
>
We have a custom script on the forge-allura.apache.org server to sync the
official git repo (git-wip-us.apache.org) over to our allura server to show up
in the code browser. Right now the script only notices changes on the master
branch. (After something is updated on master it will do a pull and get
branches then)
Of course it would be better to have it pick up on branch and tag changes, not
just master, but that's how it is right now. And its not really a problem for
development since your branches really are there.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><