latest 20 messages by raphink

+ [2016-09-13T12:29:46Z] raphink Ice_Strike, like I said, it's per repo, not per file/dir
+ [2016-09-13T11:41:18Z] raphink settings/collaboration
+ [2016-09-13T11:23:27Z] raphink Ice_Strike, access settings are per repo
+ [2016-09-07T14:14:54Z] raphink if you use shift, you can select a range, too
+ [2016-09-07T14:14:49Z] raphink that'll give you a link to the line
+ [2016-09-07T14:14:44Z] raphink _ng, go to the file (or commit) view and click on the line number
+ [2016-08-24T16:33:26Z] raphink need to go now, ++
+ [2016-08-24T16:33:18Z] raphink and then go to your fork on github and open a PR to merge the "myfeat" branch of your copy into the master branch (or whichever is the reference for the project) of the project
+ [2016-08-24T16:32:46Z] raphink local> git push myorigin myfeat
+ [2016-08-24T16:32:36Z] raphink local> echo "foo" > bar && git commit -a -m "my great feature"
+ [2016-08-24T16:32:22Z] raphink local> git checkout -b myfeat
+ [2016-08-24T16:32:00Z] raphink and open the PR with that feature branch
+ [2016-08-24T16:31:54Z] raphink push to a feature branch on your own copy
+ [2016-08-24T16:31:09Z] raphink do not open PRs against your master branch
+ [2016-08-24T16:31:05Z] raphink hakermania, use git branches
+ [2016-08-24T16:19:08Z] raphink welcome to the wonderful world of github then
+ [2016-08-24T16:19:01Z] raphink no problem :-)
+ [2016-08-24T15:57:24Z] raphink there's never a garantee that anyone will code it if you don't :-)
+ [2016-08-24T15:56:44Z] raphink then yes for sure, do make a PR