Tim Neems tneems

Methods of Signing Git Commits on MacOS

Last updated March 13, 2024

This Gist explains how to sign commits using gpg in a step-by-step fashion. Previously, krypt.co was heavily mentioned, but I've only recently learned they were acquired by Akamai and no longer update their previous free products. Those mentions have been removed.

Additionally, 1Password now supports signing Git commits with SSH keys and makes it pretty easy-plus you can easily configure Git Tower to use it for both signing and ssh.

For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing your commits with GPG.

Generate the list yourself:

$ cd /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS*.sdk/System/Library/Frameworks/UIKit.framework/Headers
$ grep UI_APPEARANCE_SELECTOR ./*     | \
  sed 's/NS_AVAILABLE_IOS(.*)//g'     | \
  sed 's/NS_DEPRECATED_IOS(.*)//g'    | \
  sed 's/API_AVAILABLE(.*)//g'        | \
  sed 's/API_UNAVAILABLE(.*)//g'      | \
 sed 's/UI_APPEARANCE_SELECTOR//g' | \

Proposal for Improving Mass Assignment

For a while, I have felt that the following is the correct way to improve the mass assignment problem without increasing the burden on new users. Now that the problem with the Rails default has been brought up again, it's a good time to revisit it.

Sign Allowed Fields

When creating a form with form_for, include a signed token including all of the fields that were created at form creation time. Only these fields are allowed.

To allow new known fields to be added via JS, we could add:

	#!/bin/bash
	# License: Public Domain.
	# Author: Joseph Wecker, 2012
	#
	# -- DEPRICATED --
	# This gist is slow and is missing .bashrc_once
	# Use the one in the repo instead! https://github.com/josephwecker/bashrc_dispatch
	# (Thanks gioele)
	#
	# Are you tired of trying to remember what .bashrc does vs .bash_profile vs .profile?

	# MOTIVATION: As rails apps are growing, people are noticing the drawbacks
	# of the ActiveRecord pattern. Several apps I have seen, and several
	# developers I have spoken to are looking towards other patterns for object
	# persistence. The major drawback with ActiveRecord is that the notion
	# of the domain object is conflated with what it means to store/retrieve
	# it in any given format (like sql, json, key/value, etc).
	#
	# This is an attempt to codify the Repository pattern in a way that would
	# feel comfortable to beginner and seasoned Ruby developers alike.
	#

	full_data = {
	response: {body: StyledYAML.literal(DATA.read), status: 200},
	person: StyledYAML.inline('name' => 'Steve', 'age' => 24),
	array: StyledYAML.inline(%w[ apples bananas oranges ])
	}

	StyledYAML.dump full_data, $stdout

	__END__
	{

	class PostsController < ActionController::Base
	def create
	Post.create(post_params)
	end

	def update
	Post.find(params[:id]).update_attributes!(post_params)
	end

	private

	@interface UILabel (dynamicSizeMe)

	-(float)resizeToFit;
	-(float)expectedHeight;

	@end

	# If your workers are inactive for a long period of time, they'll lose
	# their MySQL connection.
	#
	# This hack ensures we re-connect whenever a connection is
	# lost. Because, really. why not?
	#
	# Stick this in RAILS_ROOT/config/initializers/connection_fix.rb (or somewhere similar)
	#
	# From:
	# http://coderrr.wordpress.com/2009/01/08/activerecord-threading-issues-and-resolutions/