-Eric
On 10/13/11 6:35 PM, Cris J Holdorph wrote:
I followed those instructions before I sent my message. However, there are two problems.One, it's not clear that you have to do the pull request from your fork. If you're viewing the original repository, you see a 'pull requests' tab, and so as a NEW UNFAMILIAR user, you might be there, click on that tab, see the 'list' of requests (or empty list) and not know how to submit one. You must be on your own repo fork, but that's not clear in those instructions.Two, even when you get to your own repo and find the right screen to submit a pull request, you end up at this screen:http://img.skitch.com/20100831-qit9sjhuqk42t4ww91ifm5tm81.pngExcept in your case those two text fields will be blank, with NO indication what information should go in those text fields and no mention in the instructions about what should go in there.I guessed and submitted mine, but I had no idea if it would even work, when I pressed the 'send pull request' button.---- Cris J H On 10/13/2011 04:28 PM, Eric Dalquist wrote:The "Step-by-step (the short version)" section here https://github.com/diaspora/diaspora/wiki/Git-Workflow has good info, for something as simple as this you can skip a bunch of the steps (setting upstream remote and creating dev branch) and boil it down to: 1. Fork on GitHub (click Fork button) 2. Clone to computer ($ git clone [email protected]:you/diaspora.git ) 3. Don’t forget to cd into your repo: ($ cd diaspora/ ) 4. Make changes// 5. Commit changes to issue branch. ($ git add . ; git commit -m ‘commit message’) 6. Push branch to GitHub ($ git push) 7. Issue pull request (Click Pull Request button) Post migration I'm going to be encouraging people to follow the full set of steps and do all development on branches. That should let everyone get the work they are doing out into a visible location earlier in the development cycle and keep trunk (master) more stable. -Eric On 10/13/11 6:12 PM, Cris J Holdorph wrote:I don't see any way to submit a pull request for https://github.com/Jasig/svn2git-migration ---- Cris J H ps. I tried to do it the github way, but in any case, my github email address was/is [email protected] On 10/13/2011 03:51 PM, Eric Dalquist wrote:Thought I had found a few people by guessing usernames but the accountsdidn't have enough publicly available info for me to verify. So that email was likely from being added and then removed from the team. I'll still need the "Full Name <[email protected]>" string for the conversion if you care about commit history. -Eric On 10/13/11 5:06 PM, Cris J Holdorph wrote:I got an email from github that said: View team: https://github.com/organizations/Jasig/teams/68892 but when I got there, I get a github 404. Any ideas? ---- Cris J H On 10/13/2011 02:20 PM, Eric Dalquist wrote:Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal I've done a final test migration of the uPortal SVN repository to: https://github.com/edalquist/uPortal-GitTest *Account Mapping*This is using best author mapping data that we could put together fromthose that explicitly have listed their git accounts [1] and account information for jasig SVN committers that was compiled from the Confluence/Jira services [2]. If you have ever commit to a Jasig project in the past and think you may ever commit to uPortal (or make a pullrequest) it would be great to have you setup a GitHub account and getthe appropriate mapping information added to file [1]. [1]https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt[2]https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txtThe following people currently have commit access to uPortal but have NOT yet setup an account on GitHub, meaning that their commit historywon't transfer AND they won't be able to commit once we've moved. Please either email me your GitHub account info (should look like: Eric Dalquist <[email protected]>) or event better, get to know git and fork https://github.com/Jasig/svn2git-migration add yourself to mappedAuthors.txt and then make a pull request. * Andrew Wills (awills) * Andy Gherna (agherna) * Anthony Colebourne (acolebourne) * Brad Szabo (bszabo) * Cris Holdorph (holdorph) * Gary Thompson (gthompson) * Lennard Fuller (lfuller) * Matthew Polizzotti ([email protected]) * Susan Bramhall ([email protected]) *Scheduling* 10/20 - Thursday 10:00am CDT - https://source.jasig.org/uPortal is made read-only 4:00pm CDT - https://github.com/Jasig/uPortal will be live and available for uPortal committersUnless there are objections the schedule will proceed as stated above.Realistically the GitHub repo should be available much earlier than 4pm but don't plan on making any commits to uPortal on Thursday 10/20 and if you have any work in progress make sure it is committed somewhere (create a temporary branch if needed) so that you don't have to re-apply the changes on the git side of things. -Eric
smime.p7s
Description: S/MIME Cryptographic Signature
