7hunderbird

#!/usr/bin/env bash

set -eux

# download bucc https://github.com/starkandwayne/bucc
# this file can be embedded in the repo root

# our source code for the Cloud Foundry deployment
CF_DEPLOYMENT=src/cf-deployment

mattbennett

""" Regression tests for https://github.com/nameko/nameko/issues/428

The tests in this module show detailed examples of possible failures caused
by the above bug. It's being left here rather than in the repo since the tests
themselves are quite slow, and one is sufficient to verify the regression.

"""
import itertools
import time
from functools import partial

0xjac

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

1. Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

git clone --bare git@github.com:usi-systems/easytrace.git

robertpainsi

How to reopen a pull-request after a force-push?

Precodinitions

• You need the rights to reopen pull requests on the repository.
• The pull request hasn't been merged, just closed.

Instructions

1. Write down the current commit hash of your PR-branch git log --oneline -1 <PR-BRANCH>
2. Write down the latest commit hash on github before the PR has been closed.
3. git push -f origin :