+ [2020-06-25T18:40:21Z] ncuxo nope I've read the rtfm and found some errors and wanted to correct them
+ [2020-06-25T18:40:28Z] ncuxo I have nothing to do with the project
+ [2020-06-25T18:41:08Z] Soliton then there is no way around a fork.
+ [2020-06-25T18:46:00Z] ncuxo so I have to always fork then edit the file not on my fork but the repo I want to edit ... now I get it
+ [2020-06-25T18:47:34Z] Soliton no, you edit on your fork. github will manage that for you if you try to edit a file on a repo you have no commit access to.

message no. 182789

Posted by Henry151 in #github at 2020-06-25T13:22:08Z

especially since there are only 5 or 6 relatively small commits to deal with, I could just walk through them each manually and re-create the commit history over on this new branch. But there has to be a way to just go in there and edit something to say, "these commits belong on this other branch, not on master!"
+ [2020-06-26T09:55:40Z] faceface I'm so used to rebasing, that I suddenly don't know how to merge...
+ [2020-06-26T09:55:53Z] faceface I have a feature branch... How do I make it up to date with a development branch?
+ [2020-06-26T09:56:04Z] faceface prior to creating a merge request?
+ [2020-06-26T09:57:50Z] faceface git checkout feature1 / git merge dev