title: Git(hub) forking own repo - pull requests
body: <p>So I have project1 which contains all of the code so that it itself can run correctly. Project2 uses the same codebase as project1 but with modifications, new features etc.</p>
  
  <p>Given the 2 projects have slightly different goals, I work on them independently, but if theres some common code (like a bug fix) that is suitable in both projects, I will make the change in one, and make a pull request to the other. Otherwise, the 2 projects just act as if they're not aware of one another</p>
  
  <p>How do I set up this type of workflow on github? I've read a number of threads/questions here about how to fork your own repo, but thats not my problem</p>
  
  <p>So far, I have:</p>
  
  <ul>
  <li>Created a new blank repo (project2)</li>
  <li>cloned project2 to my machine</li>
  <li>Added a new upstream remote (project1)</li>
  <li>Pulled down the changes from upstream</li>
  <li>Pushed the code from project2 up to the project2 repo</li>
  </ul>
  
  <p>In essence this gives me a full copy of project1, but in project2 repo. I can do the usual thing of committing and pushing to each repo independently so that solves half of my problems</p>
  
  <p>Now, if theres something like a bug fix that needs to be committed and pushed to both, how do I do it?</p>
  
  <p>When I go to project2 on github and click on pull requests, I can only see requests made from project2 branches, and project2 forks. I see nothing from project1. Likewise for when I check pull requests from project1.</p>
  
  <p>the 2 projects cant see each other which makes it different from an actual fork (I think?), so how do I fix a bug and create pull requests from across these 2 repos?</p>
  
  <p>Or is there a better/more appropriate way to handle 2 slightly different repos where you want to be able to make pull requests and merge in common changes for both projects?</p>