Move from Google Code to Github

[Daniel Lee]

Unless anyone objects, I suggest moving from google code to github immediately after our next release.

I can handle the migration.

You will need a github account (http://github.com). Once you have one, let me know. I just created a stan-dev organization.

Daniel

[Marcus Brubaker]

Out of curiosity, is there a specific reason for this move?

Cheers,

Marcus

--
 
 

[Michael Betancourt]

I'm on at betanalpha

> --
>
>

[Matt Hoffman]

I'm heywhoah.

> --
>
>

[Andrew Gelman]

I'm andrewgelman

[Jiqiang Guo]

I use id maverickg.

--
 
 

[Marcus Brubaker]

User id: mbrubake

Cheers,

Marcus

[Daniel Lee]

On Thu, Jan 24, 2013 at 6:13 PM, Marcus Brubaker <marcus.a...@gmail.com> wrote:

Out of curiosity, is there a specific reason for this move?

 We've been talking about it for a while. I figure it's as good a time as any.

I've added Michael, Matt, Andrew, Bob, Marcus, Jiqiang, and myself to the stan-dev organization as owners. If anyone has suggestions on permissions settings or on migration, let me know.


Daniel

[Marcus Brubaker]

On Fri, Jan 25, 2013 at 1:01 PM, Daniel Lee <bea...@alum.mit.edu> wrote:

If anyone has suggestions on permissions settings or on migration, let me know.

Once the migration is done it would be helpful to git newbies (such as myself) if someone could post a rough set of instructions on how to make our current repositories point to the new one.  In particular, I have some local branches that I'd rather not loose or have to manually port over.

Cheers,

Marcus

[Bob Carpenter]

Will you have access to the machine with the local
branches when you're here? If so, we can help you
push those branches back to the origin (now Google code)
before we migrate.

Otherwise, git makes it pretty easy to calculate a patch
and then apply it.

I don't know if there's a way to have the current repository

point to the new one.

- Bob



On 1/25/13 1:27 PM, Marcus Brubaker wrote:

> --
>
>

[Ben Goodrich]

I am bgoodri

Ben

[Ben Goodrich]

On Friday, January 25, 2013 1:34:19 PM UTC-5, Bob Carpenter wrote:

Will you have access to the machine with the local
branches when you're here?  If so, we can help you
push those branches back to the origin (now Google code)
before we migrate.

Otherwise, git makes it pretty easy to calculate a patch
and then apply it.

I don't know if there's a way to have the current repository
point to the new one.

 
Under man git remote the set-url option can be used to make our laptops push and pull to Github.

Ben

[Peter Li]

I'm PeterLi2016

--
 
 

[Daniel Lee]

Thanks, all. The repository has been migrated. It was a lot easier than I thought.

https://github.com/stan-dev/stan

--
You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Daniel Lee]

We all have direct read/write access to the repository, so you should be able to do this from the command line:
git clone https://github.com/stan-dev/stan.git

A couple additional setup hints:
https://help.github.com/articles/set-up-git

[Ben Goodrich]

On Tuesday, February 5, 2013 10:49:46 PM UTC-5, Daniel Lee wrote:

We all have direct read/write access to the repository, so you should be able to do this from the command line:
git clone https://github.com/stan-dev/stan.git

Better would be to execute this on your existing tree

git remote set-url origin https://github.com/stan-dev/stan https://code.google.com/p/stan/

That way whatever work in progress is still ... in progress.

Ben

[Marcus Brubaker]

That worked perfectly, thanks Ben.

[Ben Goodrich]

Is there a way to configure GitHub to send pull requests to stan-dev instead of all of us individually?

[Daniel Lee]

For my account, it's showing up under stan-dev and not my personal account. Is it still showing up on your personal pull requests? Do you have the main branch forked?

[Ben Goodrich]

On Wednesday, February 6, 2013 10:49:20 PM UTC-5, Daniel Lee wrote:

For my account, it's showing up under stan-dev and not my personal account. Is it still showing up on your personal pull requests? Do you have the main branch forked?

I haven't forked the master branch. But when Jeff pull requested, I got this (apparently forwarded when originally sent to

stan-dev/stan <st...@noreply.github.com>):

On Wed, Feb 6, 2013 at 10:00 PM, Jeffrey Arnold <notifi...@github.com> wrote:

---

You can merge this Pull Request by running

  git pull https://github.com/jrnold/stan fix-doc-multi-normal-prec

Or view, comment on, or merge it at:

  https://github.com/stan-dev/stan/pull/1

Commit Summary

• added multi_normal_prec_log

File Changes

• M src/docs/stan-reference/functions.tex (19)

Patch Links:

• https://github.com/stan-dev/stan/pull/1.patch
• https://github.com/stan-dev/stan/pull/1.diff

I just thought it would be more straightforward if that forwarded to the Google Group instead of to the individuals.

Ben

[Daniel Lee]

I understand now. I don't know how to control that. If you find it, feel free to change it.

I guess one thing we could do is add stan...@googlegroups.com or mc.sta...@gmail.com as a user. But then we'll get duplicate updates. Unless you know how to turn off notifications for pull requests.

[Ben Goodrich]

I think if you go to

https://github.com/stan-dev/stan

and click on the pull down menu labeled Unwatch, you can change yourself to "Not watching" or "Ignoring". That would probably be okay if stan...@googlegroups.com were a user that was "Watching".

Ben

[Daniel Lee]

Ben, were you able to go through with adding that email to the watch list? I haven't found a way to add an email to a watch list without creating an account.

[Daniel Lee]

I'll create an email with that account and see if I can get it configured properly.