+ [2017-02-08T23:42:32Z] preaction your repository already has everything inside of it. where what went wrong?
+ [2017-02-08T23:44:45Z] preaction like, the idea behind version control is that nothing is ever lost. changes that are wrong can be rolled back. all of the changes since the project started can be examined
+ [2017-02-08T23:57:18Z] ShapeShifter499 preaction: I'll look it over again, I'll just keep copies on my drive if it comes down to that
+ [2017-02-08T23:58:29Z] preaction you don't _need_ to do that either. your repository has, inside of it, the state of your entire project after every single commit
+ [2017-02-08T23:59:12Z] ShapeShifter499 I'm trying to compile a copy of LineageOS (Android) a phone LG Volt, somewhere along the line I forked then tried to merge then deleted. Then I forked again, this time from someone else's repo who is working on the same phone, he merged in something or other. It's a mess

message no. 163211

Posted by benaiah in #github at 2017-02-08T21:56:13Z

dumb question, but as a collaborator on a repo (https://github.com/asciimoo/wuzz), which has "approved review required" for merging PRs, submitting an approval review won't merge the PR or allow the submitter to merge it, right? The repo owner has requested that I don't merge PRs without his input, so I want to be sure.
+ [2017-02-09T00:03:49Z] ShapeShifter499 preaction: I'm lazy, sorry. I'll go over it better.
+ [2017-02-09T00:40:59Z] the_dis hello
+ [2017-02-09T00:41:02Z] the_dis git hub
+ [2017-02-10T09:16:36Z] bittin AntonioRibeiro: Thanks for your tips trying them at work now :)