![]() It's a chore to do this, but I just found a possible really simple solution (if it works, testing now): Go to that link, and you can install a github app to your account which automatically updates your repositories every hour. Initially it will show you your fork as the base, and the roll20 fork as the other - your need to switch them as described in this step. I've bolded the step which caused me the most confusion. Click “Merge Pull Request” and “Confirm Merge”. Click “Create Pull Request”, give it a name, click “Send Pull Request”. Now you should see changes where your fork needs to play “catch up”. Github first compares the base fork with yours, and will find nothing if you made no changes, so, c lick “switching the base”, which will change your fork to the base, and the original to the head fork. ![]() Click “Pull Requests” on the right, then click the “New Pull Request” button. (At the end of this post might be the easiest way, but first, the manual way which I've used several times before): Access your forked repository on Github. If you use Git its pretty easy, but most of us use the Github desktop application, and that's quite a bit more complicated. There are ways to update a fork without deleting and starting over. ![]() Sooner or later this will create conflicts. Your own files are up to date, but apart from those, the rest of your fork is frozen at the time you made it, and gets more and more out of date as time goes on. The problem is your fork doesnt automatically update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |