gwlucastrig commented on pull request #162: URL: https://github.com/apache/commons-imaging/pull/162#issuecomment-900182676
>>> I went to your repository, and realized it's forked from my fork Yes. I figured that was the wrong way to do things, but it was the only way I could get github to work. When I tried forking from the main repository, I couldn't get github to accept pull requests to your branch. I would think that the idea that a developer would need to contribute to two development paths would be commonplace. So clearly I missed something. Though Google and Github help did not reveal what that might be. On Tue, Aug 17, 2021 at 5:12 AM Bruno P. Kinoshita ***@***.***> wrote: > @gwlucastrig <https://github.com/gwlucastrig> I went to your repository, > and realized it's forked from my fork. We need to fix that, but can do that > later so you don't lose anything. > > So I went to pull requests in your repo, and clicked on create new pull > request. By default it shows the dropbox with my fork as base. I just > changed that to apache/commons-imaging, and created this PR 👍 > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/commons-imaging/pull/162#issuecomment-900129422>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEWJDYIGPUWFBD5ZSYWXBB3T5IRWFANCNFSM5CJNJUWQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> > . > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
