Skip to content

Instantly share code, notes, and snippets.

REM Install Windows ADK ( https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit )
REM If USB3.0 drivers where not already injected into PE:
REM a. download our Win7x64 USB3.0 drivers:
REM USB 3.0 Host Controller Driver: http://pc-dl.panasonic.co.jp/dl/docs/069978?dc%5B%5D=002001&lang=005&no=20&oc=001020&p1=117&p2=1170534&score=1.0&sri=10357315&trn_org=2
REM USB 3.0 Driver: http://pc-dl.panasonic.co.jp/dl/docs/069977?dc%5B%5D=002001&lang=005&no=21&oc=001020&p1=117&p2=1170534&score=1.0&sri=10357315&trn_org=2
REM d. Extract the EXEs using 7zip.
REM e. Add the extracted folder path to the DriverPath variable.
REM f. un-REM the lines to install them.
REM In SCCM07, edit the "winpe.wim" boot file ( file name does NOT include packageid ) then run "Update Dis.." against the Boot Image in the console
@Chaser324
Chaser324 / GitHub-Forking.md
Last active November 14, 2024 08:32
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j