Skip to content
Browse files

Add .github files for community

- adds issue/PR templates
- adds process on proposing changes

Signed-off-by: Alex Ellis <>
  • Loading branch information...
alexellis committed Feb 20, 2019
1 parent 96b9426 commit d080195ac0e4182994d12e940818e330aa220e26
Showing with 70 additions and 5 deletions.
  1. +38 −0 .github/
  2. +20 −0 .github/
  3. +9 −2
  4. +2 −2 Dockerfile
  5. +1 −1 Dockerfile.runtime
@@ -0,0 +1,38 @@
<!--- Provide a general summary of the issue in the Title above -->

## Expected Behaviour
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->

## Current Behaviour
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->

## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement the addition or change -->

## Steps to Reproduce (for bugs)
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->

## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->

## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->

* Docker version `docker version` (e.g. Docker 17.0.05 ):

* Operating System and version (e.g. Linux, Windows, MacOS):

* Are you using Docker Swarm or Kubernetes?

* Link to your project or a code example to reproduce issue:

@@ -0,0 +1,20 @@
## Description

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->

## How are existing users impacted? What migration steps/scripts do we need?

## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] read the [CONTRIBUTION]( guide
- [ ] signed-off my commits with `git commit -s`
- [ ] added unit tests
@@ -4,7 +4,8 @@

Here are a few guidelines for contributing:

* If you would like to contribute to the codebase **please raise an issue to propose the change**
* If you would like to contribute to the codebase then please raise an issue to propose the change or feature
* Do not work on an issue / PR until it gets a `design/approved` label from a maintainer
* Do not mix feature changes or fixes with refactoring - it makes the code harder to review and means there is more for the maintainers (with limited time) to test

* If you have found a bug please raise an issue and fill out the whole template.
@@ -13,7 +14,13 @@ Here are a few guidelines for contributing:

* Please always provide a summary of what you changed, how you did it and how it can be tested.

### License
### Compliance

All commits need to be signed-off in accordance with the Developer Certificate of Origin (DCO) as per below.

The [Derek bot]( will enforce this policy, if you need help please get in touch.

#### License

This project is licensed under the MIT License.

@@ -1,4 +1,4 @@
FROM golang:1.10.4 as build
FROM golang:1.10 as build

WORKDIR /go/src/

@@ -9,7 +9,7 @@ COPY parse_upstream.go .

RUN CGO_ENABLED=0 go build -a -installsuffix cgo --ldflags "-s -w" -o /usr/bin/inlets

FROM alpine:3.8
FROM alpine:3.9
RUN apk add --force-refresh ca-certificates

COPY --from=build /usr/bin/inlets /root/
@@ -1,4 +1,4 @@
FROM alpine:3.8
FROM alpine:3.9

WORKDIR /root/

0 comments on commit d080195

Please sign in to comment.
You can’t perform that action at this time.