GitHub Tip: Don't Remove Access Until You've Merged All Pull Requests
We had a developer quit last week so I did the most logical thing, I started deleting their access to our systems. Website login - check, QuickBooks login - check, email - check, GitHub - check. Then I started working on trying to finish some of the pull requests that he had outstanding.
That's okay there must be a conflict. 
Well this doesn't look good. 
I was able to pull down the patch manually and apply it but I kept running into conflicts that required I manually merge the patch files. I would highly recommend you at least download any pull request branches before you delete the user's access because the normal 10 second process of downloading it into my local repo ended up taking about an hour (there was a lot of going back and forth on this issue) using the git am process.
Scott Keck-Warren
Scott is the Director of Technology at WeCare Connect where he strives to provide solutions for his customers needs. He's the father of two and can be found most weekends working on projects around the house with his loving partner.
Top Posts
- Working With Soft Deletes in Laravel (By Example)
- Fixing CMake was unable to find a build program corresponding to "Unix Makefiles"
- Upgrading to Laravel 8.x
- Get The Count of the Number of Users in an AD Group
- Multiple Vagrant VMs in One Vagrantfile
- Fixing the "this is larger than GitHub's recommended maximum file size of 50.00 MB" error
- Changing the Directory Vagrant Stores the VMs In
- Accepting Android SDK Licenses From The OSX Command Line
- Fixing the 'Target class [config] does not exist' Error
- Using Rectangle to Manage MacOS Windows