Skip to content

Instantly share code, notes, and snippets.

View slovenec88's full-sized avatar

Davor Val Vega slovenec88

View GitHub Profile
@al3xtjames
al3xtjames / xps_9560_ifr.txt
Last active April 2, 2024 10:35
Dell XPS 15 9560 (1.2.5) NVRAM edits
# Set Intel(R) Speed Shift Technology to Enabled
setup_var 0x4BC 0x1
# Set CFG Lock to Disabled
setup_var 0x4ED 0x0
# Set Above 4GB MMIO BIOS assignment to Enabled
# setup_var 0x79A 0x1
# Set EHCI Hand-off to Disabled
# setup_var 0x2 0x0
# Set XHCI Hand-off to Disabled
@Chaser324
Chaser324 / GitHub-Forking.md
Last active February 20, 2025 17:06
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