cseeman

Keybase proof

I hereby claim:

• I am cseeman on github.
• I am cseeman (https://keybase.io/cseeman) on keybase.
• I have a public key ASD1MmwBPtvTc80BHxKVo13loUbuQnLBElGdnEqkA1cbLQo

To claim this, I am signing this object:

cseeman

A forking rebase wokflow with GitHub is a common Git workflow, whether you're trying to work on open source or collaborating on work projects or your own.

Knowing how to properly fork and generate pull requests is essential.

It is easy to make mistakes when you're learning the process. In an attempt to gather this information for myself and others, this short tutorial for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

On the GitHub page and click the "Fork" button. Once you've done that, you can use your favorite git client to clone your repo or just head straight to the command line (my method of choice):

cseeman

[alias]
  asq    = !sh -c 'git rip $1^ --autosquash' -
  b      = branch
  can    = commit -v --amend --no-edit
  cgf    = checkout Gemfile Gemfile.lock
  ci     = commit -v
  cia    = commit -v --amend
  co     = checkout
  cp     = cherry-pick
  d      = diff

cseeman

#
# ~/.gitconfig 
#


[user]
	name = Christine Seeman
	mail = 
	email = 

cseeman

sequenceDiagram;
    participant C as Client
    participant O as Resource Owner
    participant A as Authorization Server
    participant R as Resource Server
    
    C->>O: requests authorization 
    O->>C: receives authorization grant
 C->>A: requests access token, presents grant

cseeman

sequenceDiagram;
    participant C as Client + Resource Owner
    participant A as Authorization Server
    participant R as Resource Server
    
    C->>A: 1. Request access token (POST /token) 
    A->>C: 2. Respone with access token
    C->>R: 3. Request with access token
 R->>C: 4. Response

cseeman

Examples for how to create your own info panel, warning box and other decent looking notification in GitHub markdown.

All the boxes are single/two cell tables or two row tables.

Warning box

❗ You have to read about this

cseeman

Updating a feature branch

First we'll update your local develop branch. Go to your local project and check out the branch you want to merge into (your local develop branch)

$ git checkout develop

Fetch the remote, bringing the branches and their commits from the remote repository. You can use the -p, --prune option to delete any remote-tracking references that no longer exist in the remote. Commits to develop will be stored in a local branch, remotes/origin/develop

cseeman

# Generic Ruby Gem Release Workflow (with RubyGems Trusted Publishing)
# 
# This workflow demonstrates a streamlined Ruby gem release process using:
# - Reissue gem for version management and changelog handling, https://rubygems.org/gems/reissue
# - Discharger gem for release automation (optional, https://rubygems.org/gems/discharger/)
# - RubyGems Trusted Publishing for secure, keyless authentication
# - Single-click releases with automatic version bumping
#
# Prerequisites:
# 1. Configure RubyGems Trusted Publisher at https://rubygems.org/gems/YOUR_GEM