Merge pull request #18 from mchmarny/master

Custom go SDK (aka bespoke client proposal)

Author: mchmarny

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,47 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - 'v*' # v0.8.1
+
+jobs:
+
+  build:
+    name: Create Release
+    runs-on: ubuntu-latest
+    steps:
+
+    - name: Setup
+      id: go
+      uses: actions/setup-go@v2
+      with:
+        go-version: ^1.14
+
+    - name: Checkout
+      id: setup
+      uses: actions/checkout@v2
+
+    - name: Tidy
+      run: |
+        go mod tidy 
+        go mod vendor
+
+    - name: Test
+      run: go test -v -count=1 -race ./...
+
+    - name: Version
+      id: get_version
+      run: echo ::set-env name=RELEASE_VERSION::$(echo ${GITHUB_REF:10})
+      
+    - name: Release
+      id: release-step
+      uses: actions/create-release@v1
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        tag_name: ${{ github.ref }}
+        release_name: Release ${{ github.ref }}
+        body: Automatic go Dapr client release 
+        draft: false
+        prerelease: false

.github/ISSUE_TEMPLATE/discussion.md

@@ -0,0 +1,31 @@
+name: Test
+
+on:
+  push:
+
+jobs:
+
+  build:
+    name: Test Push
+    runs-on: ubuntu-latest
+    steps:
+
+    - name: Setup
+      id: go
+      uses: actions/setup-go@v2
+      with:
+        go-version: ^1.14
+
+    - name: Checkout
+      id: setup
+      uses: actions/checkout@v2
+
+    - name: Tidy
+      run: |
+        go mod tidy 
+        go mod vendor
+
+    - name: Test
+      run: go test -v -count=1 -race ./...
+      
+    

.github/ISSUE_TEMPLATE/feature_request.md

@@ -10,3 +10,10 @@
 
 # Output of the go coverage tool, specifically when used with LiteIDE
 *.out
+.DS_Store
+
+# vendor 
+vendor
+
+# docs 
+golang.org

.github/ISSUE_TEMPLATE/proposal.md

@@ -1,6 +1,6 @@
 # Contribution Guidelines
 
-Thank you for your interest in Dapr!
+Thank you for your interest in Dapr go SDK!
 
 This project welcomes contributions and suggestions. Most contributions require you to
 agree to a Contributor License Agreement (CLA) declaring that you have the right to,
@@ -37,18 +37,13 @@ There are 4 types of issues:
 
 Before you file an issue, make sure you've checked the following:
 
-1. Is it the right repository?
-    - The Dapr project is distributed across multiple repositories. Check the list of [repositories](https://github.com/dapr) if you aren't sure which repo is the correct one.
 1. Check for existing issues
     - Before you create a new issue, please do a search in [open issues](https://github.com/dapr/go-sdk/issues) to see if the issue or feature request has already been filed.
     - If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reaction-to-pull-requests-issues-and-comments). Use a reaction:
         - 👍 up-vote
         - 👎 down-vote
-1. For bugs
-    - Check it's not an environment issue. For example, if running on Kubernetes, make sure prerequisites are in place. (state stores, bindings, etc.)
-    - You have as much data as possible. This usually comes in the form of logs and/or stacktrace. If running on Kubernetes or other environment, look at the logs of the Dapr services (runtime, operator, placement service). More details on how to get logs can be found [here](https://github.com/dapr/docs/tree/master/best-practices/troubleshooting/logs.md).
 1. For proposals
-    - Many changes to the Dapr runtime may require changes to the API. In that case, the best place to discuss the potential feature is the main [Dapr repo](https://github.com/dapr/dapr).
+    - Some changes to the Dapr go SDK may require changes to the API. In that case, the best place to discuss the potential feature is the main [Dapr repo](https://github.com/dapr/dapr).
     - Other examples could include bindings, state stores or entirely new components.
 
 ## Contributing to Dapr