Skip to content

Commit

Permalink
Merge branch 'master' into feature/housekeeping
Browse files Browse the repository at this point in the history
  • Loading branch information
Kieranties committed Apr 9, 2019
2 parents fa7f638 + e9a37e9 commit 2538c1a
Show file tree
Hide file tree
Showing 5 changed files with 89 additions and 1 deletion.
33 changes: 33 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
name: Bug report
about: Raise a bug that needs fixing
title: ''
labels: ":bug: bug"
assignees: ''

---

**Describe the bug**
Please provide as much info as possible.

**Reproduction steps**
Steps to reproduce the behavior (if possible provide configuration and other assets as attachment)
1. Go to '...'
2. Run '....'

**Expected behavior**
A clear and concise description of what you expected to happen.

**Actual Behavior**
A clear and concise description on what you are actually seeing

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Environment**
- OS: [e.g. Windows]
- Implementation: [e.g. Commandline, Cake, Libraries]
- Version [e.g. 0.1.0]

**Additional context**
Add any other context about the problem here.
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: ":sparkles: feature"
assignees: ''

---

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
14 changes: 14 additions & 0 deletions .github/ISSUE_TEMPLATE/information-request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
name: Information request
about: Raise queries and get guidance
title: ''
labels: ":question: question"
assignees: ''

---

**What do you need to know?**
Explain as simply as possible the topic area

**Does any existing documentation or sample confuse things?**
Provide information on any material which is unclear, or hinders your understanding
20 changes: 20 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# Description
Provide a detailed description of the changes provided in this PR

Fixes # (provide one or more issues this PR fixes)

## Change Type

- [ ] Documentation: Changes to docs are included
- [ ] Infrastructure: Changes to build scripts/non-deliverables
- [ ] Bug Fix: Fixes an issue in implementation
- [ ] New Feature: Adds new functionality in a non-breaking manner
- [ ] Breaking Change: Implements a fix or feature in a breaking manner

# Quality
- [ ] Unit tests have been added/updated
- [ ] Local builds/testing are successfull
- [ ] Code coverage has not decreased
- [ ] Code comments have been provided (where appropriate)
- [ ] Core styles have been followed
- [ ] Documentation has been added/updated
3 changes: 2 additions & 1 deletion azure-pipelines.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ trigger:
paths:
exclude:
- docs/*
- .github/*
- README.md

pr:
Expand Down Expand Up @@ -45,7 +46,7 @@ jobs:
$fullVersion = ($result | ConvertFrom-Json).Formats.Semver2
Write-Output "##vso[build.updatebuildnumber]$fullVersion"
Write-Output "##vso[task.setvariable variable=Version;]$fullVersion"
Write-Output "##vso[build.addbuildtag]build/$fullVersion"
Write-Output "##vso[build.addbuildtag]build/$fullVersion"
displayName: 'Prepare: Set version information'
# Build/Pack the assets
Expand Down

0 comments on commit 2538c1a

Please sign in to comment.