...
[15:44:07 CDT(-0500)] <EricDalquist> now if you go to your fork you should see that master there matches up with master in jasig/uPortal
[15:44:25 CDT(-0500)] <EricDalquist> the next question ... is there anything in your local commits on your branch off of 4.0.5 that is private?
[15:44:33 CDT(-0500)] <JoeMoore> authored 4 hours ago
[15:44:35 CDT(-0500)] <JoeMoore> perfect
[15:44:52 CDT(-0500)] <EricDalquist> because with the free account your fork is publicly visible
[15:44:53 CDT(-0500)] <JoeMoore> yes, there are some passwords
[15:44:57 CDT(-0500)] <EricDalquist> ok
[15:45:02 CDT(-0500)] <EricDalquist> so we can't do this next step
[15:45:08 CDT(-0500)] <EricDalquist> until you get yourself a private repository
[15:45:13 CDT(-0500)] <EricDalquist> either by paying github
[15:45:43 CDT(-0500)] <EricDalquist> or setting up some sort of local git hosting solution (a very simple local git host is a server you can ssh to that has git installed on it)
[15:46:07 CDT(-0500)] <JoeMoore> OK, Ill need to think about the pros and cons of that.
[15:46:09 CDT(-0500)] <EricDalquist> the next step if you have a private repo would be "git push origin your4.0.5branchname"
[15:46:43 CDT(-0500)] <EricDalquist> you need to do that to push a branch that only exists locally to a remote where the branch does not exist yet
[15:47:04 CDT(-0500)] <EricDalquist> after that "git push origin" will push changes to all branches that the remote knows about
[15:47:26 CDT(-0500)] <EricDalquist> also ... lets say 4.0.6 comes out tomorrow and you want to upgrade your branch to it
[15:47:34 CDT(-0500)] <JoeMoore> makes sense
[15:47:36 CDT(-0500)] <EricDalquist> you would do "git merge uportal-4.0.6"
[15:48:00 CDT(-0500)] <EricDalquist> that will take all the commits that have happened from 4.0.5 and 4.0.6 in the jasig/uportal/master branch
[15:48:04 CDT(-0500)] <EricDalquist> and merge them into your branch
[15:48:43 CDT(-0500)] <EricDalquist> I know that was a lot of stuff
[15:48:50 CDT(-0500)] <EricDalquist> but hopefully you're feeling a little better about git
[15:48:58 CDT(-0500)] <EricDalquist> I'm going through and updating our git workflow docs
[15:49:11 CDT(-0500)] <EricDalquist> and will try and clarify a bunch of stuff
[15:49:24 CDT(-0500)] <JoeMoore> so do those last statements about upgrading apply without pushing origin back?
[15:49:40 CDT(-0500)] <EricDalquist> yes
[15:50:03 CDT(-0500)] <EricDalquist> the only reason you would want to do the "git push origin yourbranch" is to have a shared location for the branch
[15:50:11 CDT(-0500)] <EricDalquist> like if another dev on your team wanted to work on that same branch
[15:50:14 CDT(-0500)] <EricDalquist> or you wanted a backup
[15:50:24 CDT(-0500)] <EricDalquist> if you're happy just working on your local repository
[15:50:31 CDT(-0500)] <EricDalquist> you don't need origin at all
[15:52:04 CDT(-0500)] <JoeMoore> I thought so. Thank you! I'm saving the pointer to this log. Now I'll go back and try to redo my ant commands against my pristine 4.0.5 with local changes after checking pom.xml in cas
[15:52:15 CDT(-0500)] <EricDalquist> sounds good
[15:52:23 CDT(-0500)] <EricDalquist> hopefully we can have better wiki docs before I go home today too 
[16:02:05 CDT(-0500)] <peterjhart> EricDalquist: the SCSS builds fine for me. There are a few differences between the resulting portal.css and the portal.css in master. I can't look into it right now, though