Skip to content
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.

Commit

Permalink
Add Github code owner and PR template files, and fix release pipeline…
Browse files Browse the repository at this point in the history
… issue (#7)

## What is the goal of this PR?

- We have fixed a release pipeline issue causing the maven artifact to not be released
- We have added Github code owner and PR template files
  • Loading branch information
Ganeshwara Herawan Hananda authored Dec 4, 2019
1 parent 2068be9 commit 36613c2
Show file tree
Hide file tree
Showing 7 changed files with 97 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -263,7 +263,7 @@ workflows:
- deploy-maven-release:
filters:
branches:
only: client-java-release-branch
only: common-release-branch
requires:
- deploy-approval
- deploy-apt:
Expand Down
1 change: 1 addition & 0 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* @haikalpribadi @flyingsilverfin
41 changes: 41 additions & 0 deletions .github/ISSUE_TEMPLATE/BUG_REPORT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
---
name: Bug Report
about: Report a bug here, or visit discuss.grakn.ai for troubleshooting discussions
title: ''
labels: bug
assignees: ''

---

Please replace every line in curly brackets { like this } with an appropriate answer, and remove this line.

## Description

{ Please provide a clear and concise description of the bug. }

## Environment

1. OS (where Grakn server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
2. Grakn version (and platform): { e.g. Grakn Core 1.4, or Grakn KGMS 1.4.3 on Google Cloud }
3. Grakn client: { e.g. client-java, client-python, client-nodejs, or console }
4. Other environment details:

## Reproducible Steps

Steps to create the smallest reproducible scenario:
1. { e.g. Run ... }
2. { e.g. Load ... }
3. { e.g. Query ... }
4. { e.g. See error ... }

## Expected Output

{ Please describe what you expected to happen. }

## Actual Output

{ Please describe what actually happened. }

## Additional information

{ Any additional information, including logs or screenshots if you have any. }
26 changes: 26 additions & 0 deletions .github/ISSUE_TEMPLATE/FEATURE_REQUEST.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
name: Feature Request
about: Request a feature here, or visit discuss.grakn.ai for ideas and questions
title: ''
labels: feature
assignees: ''

---

Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.

## Problem to Solve

{ Please describe the problem you would like to solve. }

## Current Workaround

{ Please describe how you currently solve or work around this problem, given Grakn's limitation. }

## Proposed Solution

{ Please describe the solution you would like Grakn to provide, to solve the problem above. }

## Additional Information

{ Any additional information, including logs or screenshots if you have any. }
15 changes: 15 additions & 0 deletions .github/ISSUE_TEMPLATE/REFACTOR.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
name: Refactor
about: Propose an architecture refactor here
labels: refactor
---

Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.

## Problem to Solve

{ Please describe the problem with the current architecture that you would like to solve. }

## Proposed Solution

{ Please describe how you would like to change the architecture, to solve the problem above. }
12 changes: 12 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
Please replace every line in curly brackets ( { like this } ) with an appropriate description, and remove this line.

## What is the goal of this PR?

{ In the form of a paragraph (only use bullet points if strictly necessary), please describe the goal of this PR, why they are valuable to achieve, and reference the related GitHub issues. This section will be automatically compiled into the release notes, so please:
- describe the impact of the change in this PR to the _user_ of this repository (e.g. end user, contributor, developer).
- describe the new product behaviour in _present tense_, and the old behaviour and how it's been changed in _past tense_.
- Use the _Royal We_: _"We"_ made changes, not _"I"_ made changes. }

## What are the changes implemented in this PR?

{ Please explain what you implemented, why your changes are the best way to achieve the goal(s) above, and reference the GitHub issues to be automatically closed, such like 'closes #number'. }
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.2.1
0.2.2

0 comments on commit 36613c2

Please sign in to comment.