latest 20 messages by jpalmer
+
[2014-12-30T22:12:24Z]
jpalmer
when you fork it, you basically make a copy of their repo. you can modify that copy as much as you want, and it has nothing to do with their repo. including contributions. it's only when you push those changes upstream to their repo, will you show as a contributor.
+
[2014-12-30T22:11:10Z]
jpalmer
If you forked it, and you are only pushing changes to your fork of it, you'll be listed as a contributor in your fork, but not in the upstream project unless you contribue a pull request to them, and they accept it and merge it into master
+
[2014-12-30T22:10:21Z]
jpalmer
well, the way github works is, you'll be listed as a contributor when work you've done is merged into master on the repo.
+
[2014-12-30T22:03:35Z]
jpalmer
brb, feeding horses while you answer.
+
[2014-12-30T22:02:59Z]
jpalmer
wykydtron: when you say "doesn't recognize contributors" what exactly do you mean?
+
[2014-12-30T00:54:40Z]
jpalmer
no, however.. MY new years resolution is to start blogging more on topics that interest me (and hence, here I am!) so it might be a good follow up when the current series (of 4 articles) is done.
+
[2014-12-30T00:51:05Z]
jpalmer
cripes. that was 2007. now I feel old.
+
[2014-12-30T00:50:01Z]
jpalmer
apparently, it's still online. hehe
+
[2014-12-30T00:49:51Z]
jpalmer
http://www.onlamp.com/pub/a/bsd/2007/09/27/subversion-for-bsd-with-all-the-bells-and-whistles.html
+
[2014-12-30T00:49:07Z]
jpalmer
wrote an article several years ago for onlamp magazine (o'rielly) on a pretty nice trac/svn setup. but now I'm entirely git
+
[2014-12-30T00:48:25Z]
jpalmer
yep. trac has git plugins now :P
+
[2014-12-30T00:46:40Z]
jpalmer
or, as painless as it can be when more than one person is editing the same thing, I guess.
+
[2014-12-30T00:46:26Z]
jpalmer
svn makes branching and merging insanely difficult, when compared to git. git makes branching/merging painless.
+
[2014-12-30T00:45:54Z]
jpalmer
I've heard a *lot* of projects that used SVN say "well, we're using git for this new piece over here.. but the MAIN one will always be svn" and then fast-forward a few months, and it's all git.
+
[2014-12-30T00:43:27Z]
jpalmer
git is a great tool to learn, for sure.
+
[2014-12-30T00:43:08Z]
jpalmer
btw, when you get it pushed to master, and have all your code back.. you can do "git push origin :source" (note the : in :source) and that will delete the remote 'source' branch at github.
+
[2014-12-30T00:41:42Z]
jpalmer
but github pages, only looks at 'master' so pushing those changes into 'source' or any other branch, is just going to be ignored.
+
[2014-12-30T00:41:06Z]
jpalmer
if you go to githubs web interface, and look at the "branches" for your repo, you'll see you have 2 (or more) now.
+
[2014-12-30T00:40:44Z]
jpalmer
it didn't get confused, it just pushed your changed to a new branch that github doesn't use for the github pages stuff ;)
+
[2014-12-30T00:39:20Z]
jpalmer
cool. good work