Skip to content

Instantly share code, notes, and snippets.

View stefanbuck's full-sized avatar
:octocat:

Stefan Buck stefanbuck

:octocat:
View GitHub Profile
@stefanbuck
stefanbuck / upload-github-release-asset.sh
Last active November 26, 2023 12:40
Script to upload a release asset using the GitHub API v3.
#!/usr/bin/env bash
#
# Author: Stefan Buck
# License: MIT
# https://gist.github.com/stefanbuck/ce788fee19ab6eb0b4447a85fc99f447
#
#
# This script accepts the following parameters:
#
# * owner
@stefanbuck
stefanbuck / prepare-commit-msg
Last active June 9, 2023 21:09
Ticket number git hook
#!/usr/bin/env bash
#
# Authors:
# Stefan Buck (https://github.com/stefanbuck)
# Thomas Ruoff (https://github.com/tomru)
#
#
# Description:
# Are you still prefixing your commits with a ticket number manually? You will love this script!
# This is a git hook script that will automatically prefix your commit messages with a ticket

Octoherd script to help with the recent CircleCI’s security breach by removing deploy keys from your repos.

No warranty, use at your own risk!

Dry-run

Run the script on a single repo first. Octoherd will prompt to confim the deletion request.

const alphabet = 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ';
const input = [
"I really",
"ScriptJava",
["and I", "an it's"],
{
m1: "love",
m2: "!namuh retteb a"
},
@stefanbuck
stefanbuck / github_action.sh
Created October 21, 2021 07:32
GitHub shell options
#!/bin/bash --noprofile --norc -e -o pipefail {0}
#!/usr/bin/env ruby
require 'open-uri'
require 'pathname'
require 'json'
def strip_hash(f)
ext = f.extname
if ext.include?("?")
@stefanbuck
stefanbuck / GitHub-Forking.md
Created December 19, 2018 18:51 — forked from Chaser324/GitHub-Forking.md
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

@stefanbuck
stefanbuck / docker-health.sh
Created February 7, 2018 07:52
Returns the health status for the given docker image
#!/usr/bin/env bash
IMAGE_NAME=$1
# Grep container id
CONTAINER_ID=$(docker ps -qf "name=$IMAGE_NAME")
if [ "$CONTAINER_ID" ] ; then
# Get the health status
STATUS=$(docker inspect --format='{{json .State.Health.Status}}' $CONTAINER_ID);
<project>
<actions/>
<description/>
<keepDependencies>false</keepDependencies>
<properties>
<com.sonyericsson.jenkins.plugins.bfa.model.ScannerJobProperty plugin="build-failure-analyzer@1.19.0">
<doNotScan>false</doNotScan>
</com.sonyericsson.jenkins.plugins.bfa.model.ScannerJobProperty>
<com.chikli.hudson.plugin.naginator.NaginatorOptOutProperty plugin="naginator@1.17.2">
<optOut>false</optOut>