Skip to content

Commit

Permalink
Merge branch 'main' into fix-warnings
Browse files Browse the repository at this point in the history
  • Loading branch information
miquelbeltran authored Jul 17, 2024
2 parents 579544d + 9143caf commit 3d3685e
Show file tree
Hide file tree
Showing 5 changed files with 164 additions and 0 deletions.
45 changes: 45 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
name: Bug report
about: Bug report
title: "<Area of the SDK>: <Short Description of issue>"
labels: needs triage
assignees: ''

---

**Describe the bug**

A clear and concise description of what the bug is.

**To Reproduce**

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**

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

Links to related tickets or other context are welcome here.

**Screenshots**

If applicable, add screenshots to help explain your problem.

**Environment (please complete the following information):**

- OS: [e.g. Linux/Windows/macOS etc]
- SDK version: [e.g. 1.2.3]
- Dotnet versions: [e.g. 8.0.7]

**Logs**

If applicable, include relevant logs or error messages here (please use code blocks to format properly).

**Possible Solution**

If you have suggestions for how the issue might be resolved or investigated, please describe them here.
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: A new feature for this SDK
title: "<Area of the SDK>: <Short Description of new feature>"
labels: needs triage
assignees: ''

---

**Please describe your new feature request**

A clear and concise description of what the problem is. Example: I'm always frustrated when [...]

**Describe the solution you'd like**

A clear and concise description of what you want to happen.

Links to related tickets or other information are welcome here.

**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.
9 changes: 9 additions & 0 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
version: 2
updates:
- package-ecosystem: "nuget"
directory: "/src"
schedule:
interval: "weekly"
commit-message:
prefix: "chore"
include: "scope"
37 changes: 37 additions & 0 deletions .github/workflows/pr.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
name: "Pull-Request Check"

on:
pull_request:
types:
- opened
- edited
- synchronize

jobs:
main:
name: Validate PR title
runs-on: ubuntu-latest
steps:
- uses: amannn/action-semantic-pull-request@v5
id: lint_pr_title
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- uses: marocchino/sticky-pull-request-comment@v2
# When the previous steps fails, the workflow would stop. By adding this
# condition you can continue the execution with the populated error message.
if: always() && (steps.lint_pr_title.outputs.error_message != null)
with:
header: pr-title-lint-error
message: |
We require pull request titles to follow the [Conventional Commits specification](https://www.conventionalcommits.org/en/v1.0.0/) and it looks like your proposed title needs to be adjusted.
Details:
```
${{ steps.lint_pr_title.outputs.error_message }}
```
# Delete a previous comment when the issue has been resolved
- if: ${{ steps.lint_pr_title.outputs.error_message == null }}
uses: marocchino/sticky-pull-request-comment@v2
with:
header: pr-title-lint-error
delete: true
47 changes: 47 additions & 0 deletions pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
## [{ticket number/type}:] {title}

### Description :memo:

- **Purpose**: What issue does this PR address or what feature does it implement?
- **Approach**: How does this PR tackle the problem?

**Type of change**

*Delete options that are not relevant.*

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update

**Updates**

:point_right:
:point_right:
:point_right:

### Screenshots :camera:

{Image here of before and after - if applicable}

### Test plan :test_tube:

*Provide guidance for how to QA your proposed changes. This is not only for a test but also useful for a reviewer.*

{A test plan outlining scenarios to test}

### Author to check :eyeglasses:

- [ ] Project and all contained modules builds successfully
- [ ] Self-/dev-tested
- [ ] Unit/UI/Automation/Integration tests provided where applicable
- [ ] Code is written to standards
- [ ] Appropriate documentation written (code comments, internal docs)

### Reviewer to check :heavy_check_mark:

- [ ] Project and all contained modules builds successfully
- [ ] Change has been dev-/reviewer-tested, where possible
- [ ] Unit/UI/Automation/Integration tests provided where applicable
- [ ] Code is written to standards
- [ ] Appropriate documentation written (code comments, internal docs)

0 comments on commit 3d3685e

Please sign in to comment.