- router v2.15.1 -> v2.16.0
- slugbuilder v2.7.0 -> v2.7.1
- workflow v2.20.2 -> v2.21.0
- workflow-cli v2.20.2 -> v2.21.0
- workflow-e2e v2.20.2 -> v2.21.0
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
git --git-dir=../<some_other_repo>/.git \ | |
format-patch -k -1 --stdout <commit SHA> | \ | |
git am -3 -k | |
# https://stackoverflow.com/questions/5120038/is-it-possible-to-cherry-pick-a-commit-from-another-git-repository |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
# Network Manager Dispatcher Hook: | |
# enables/disables ipv6 on vpn-down/vpn-up respectively | |
# Args | |
INTERFACE="$1" | |
ACTION="$2" | |
case $ACTION in | |
vpn-up) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# recursive.sh | |
# | |
# ./recursive.sh | |
# Segmentation fault (core dumped) | |
# | |
# set -e | |
# trap 'case $? in | |
# 139) echo "segfault occurred"; sleep 20; | |
# esac' CHLD && ./recursive.sh |
There is a fix for Helm that we need to do if we are using Helm 2.x in order to give helm enough permissions to create releases.
This is a known issue and was first found here: helm/helm#3055
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Team Hephy Code of Conduct | |
Like the technical community as a whole, the Hephy team and community is made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the mission - including mentorship, teaching, and connecting people. | |
Diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to. This code applies equally to founders, mentors and those seeking help and guidance. | |
This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the technical communities in which we participate. | |
This code of conduct applies to all spaces managed by the Hephy project. This includes IRC, the mailing lists, the issue tracker, events, and any other forums created by the project team which the community uses for communication. In addition, violations of this code outs |
NewerOlder