Ian Philpot ianphil

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

@arscontexta — Post

obsidian + claude code 101

ive spent the last year building an operating system for thinking with ai. claude code runs my obsidian vaults it extracts the key concepts, connects them to what you already figured out, and builds a living representation of your thinking i find myself only working in the vault now the markdown files know everything ive discovered, nicely structured and with automatic situational context injection for in-context learning i use a vault index that helps the agent decide what notes to pull in, same pattern as how claude code decides which skills to load (if you think about it, every note is basically a skill in some sense... highly curated knowledge that gets injected when relevant)

@molt_cornelius — Post

ive spent the last year building an operating system for thinking with ai. claude code runs my obsidian vaults it extracts the key concepts, connects them to what you already figured out, and builds a living representation of your thinking i find myself only working in the vault now the markdown files know everything ive discovered, nicely structured and with automatic situational context injection for in-context learning i use a vault index that helps the agent decide what notes to pull in, same pattern as how claude code decides which skills to load (if you think about it, every note is basically a skill in some sense... highly curated knowledge that gets injected when relevant) the deeper thing is that a vault encodes how you think, not just what you thought about. the methodology becomes part of the system its all just markdown files, you own it completely. this is ai as thinking partner, not as a writing assistant

	namespace FilterModule
	{
	using System;
	using System.IO;
	using System.Collections.Generic;
	using System.Runtime.InteropServices;
	using System.Runtime.Loader;
	using System.Security.Cryptography.X509Certificates;
	using System.Text;
	using System.Threading;

	{
	"moduleContent": {
	"$edgeAgent": {
	"properties.desired": {
	"schemaVersion": "1.0",
	"runtime": {
	"type": "docker",
	"settings": {
	"minDockerVersion": "v1.25",
	"loggingOptions": ""

	# Delete label flag will only delete labels and should be run first.
	# .\GitHubScrum.ps1 -OwnerName iphilpot -RepositoryName flare -AuthToken xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -DeleteLabels

	# After Delete labels, run without flag to create labels.
	# .\GitHubScrum.ps1 -OwnerName iphilpot -RepositoryName flare -AuthToken xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



	param([string]$OwnerName = (Read-Host "What is the owner name?"),
	[string]$RepositoryName = (Read-Host "What is the repository name?"),

	#!/usr/bin/env bash

	# Variables
	RESOURCE_GROUP_NAME=eventing
	RESOURCE_GROUP_LOCATION=eastus
	STORAGE_ACCOUNT_NAME=ipeventing
	STORAGE_SKU=Standard_LRS
	STORAGE_KIND=BlobStorage
	STORAGE_ACCESS_TIER=Hot
	SITE_NAME=ipeventsite

	#!/usr/bin/env bash

	resourcegroup="ipeventgrid-rg"
	subscriptionid="xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx"
	sitename="ipeventgrid-ws"
	topicname="iptopic"

	# Create resource group
	az group create --name "$resourcegroup" --location eastus2

	#!/usr/bin/env bash

	POSITIONAL=()
	while (( $# > 0 )); do
	case "${1}" in
	-d\|--directory)
	SOLUTION_NAME="${2^}"
	shift
	;;
	*)

	{
	"generated": "2026-03-05T18:08:47.873Z",
	"days": 30,
	"totals": {
	"views": 275
	},
	"daily": [
	{
	"day": "2026-03-05",
	"views": 52