Skip to content

Commit 9f9178c

Browse files
SimonCroppSimonCropp
committed
.
0 parents  commit 9f9178c

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

49 files changed

+1324
-0
lines changed

‎.gitattributes‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
* text
2+
*.snk binary
3+
*.pdf binary
4+
*.docx binary
5+
*.png binary
6+
*.xlsx binary
7+
*.pptx binary
8+
*.ppt binary
9+
10+
*.verified.csv text eol=lf working-tree-encoding=UTF-8
11+
*.verified.txt text eol=lf working-tree-encoding=UTF-8
12+
*.verified.xml text eol=lf working-tree-encoding=UTF-8
13+
14+
.editorconfig text eol=lf working-tree-encoding=UTF-8
15+
Shared.sln.DotSettings text eol=lf working-tree-encoding=UTF-8

‎.github/FUNDING.yml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
github: VerifyTests

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Bug fix
3+
about: Create a bug fix to help us improve
4+
---
5+
6+
Note: New issues raised, where it is clear the submitter has not read the issue template, are likely to be closed with "please read the issue template". Please don't take offense at this. It is simply a time management decision. If someone raises an issue, and can't be bothered to spend the time to read the issue template, then the project maintainers should not be expected to spend the time to read the submitted issue. Often too much time is spent going back and forth in issue comments asking for information that is outlined in the issue template.
7+
8+
9+
#### Preamble
10+
11+
General questions may be better placed [StackOveflow](https://stackoverflow.com/).
12+
13+
Where relevant, ensure you are using the current stable versions on your development stack. For example:
14+
15+
* Visual Studio
16+
* [.NET SDK or .NET Core SDK](https://www.microsoft.com/net/download)
17+
* Any related NuGet packages
18+
19+
Any code or stack traces must be properly formatted with [GitHub markdown](https://guides.github.com/features/mastering-markdown/).
20+
21+
22+
#### Describe the bug
23+
24+
A clear and concise description of what the bug is. Include any relevant version information.
25+
26+
A clear and concise description of what you expected to happen.
27+
28+
Add any other context about the problem here.
29+
30+
31+
#### Minimal Repro
32+
33+
Ensure you have replicated the bug in a minimal solution with the fewest moving parts. Often this will help point to the true cause of the problem. Upload this repro as part of the issue, preferably a public GitHub repository or a downloadable zip. The repro will allow the maintainers of this project to smoke test the any fix.
34+
35+
#### Submit a PR that fixes the bug
36+
37+
Submit a [Pull Request (PR)](https://help.github.com/articles/about-pull-requests/) that fixes the bug. Include in this PR a test that verifies the fix. If you were not able to fix the bug, a PR that illustrates your partial progress will suffice.

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
blank_issues_enabled: false

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
name: Feature request
3+
about: How to raise feature requests
4+
---
5+
6+
7+
Note: New issues raised, where it is clear the submitter has not read the issue template, are likely to be closed with "please read the issue template". Please don't take offense at this. It is simply a time management decision. If someone raises an issue, and can't be bothered to spend the time to read the issue template, then the project maintainers should not be expected to spend the time to read the submitted issue. Often too much time is spent going back and forth in issue comments asking for information that is outlined in the issue template.
8+
9+
If you are certain the feature will be accepted, it is better to raise a [Pull Request (PR)](https://help.github.com/articles/about-pull-requests/).
10+
11+
If you are uncertain if the feature will be accepted, outline the proposal below to confirm it is viable, prior to raising a PR that implements the feature.
12+
13+
Note that even if the feature is a good idea and viable, it may not be accepted since the ongoing effort in maintaining the feature may outweigh the benefit it delivers.
14+
15+
16+
#### Is the feature request related to a problem
17+
18+
A clear and concise description of what the problem is.
19+
20+
21+
#### Describe the solution
22+
23+
A clear and concise proposal of how you intend to implement the feature.
24+
25+
26+
#### Describe alternatives considered
27+
28+
A clear and concise description of any alternative solutions or features you've considered.
29+
30+
31+
#### Additional context
32+
33+
Add any other context about the feature request here.

‎.github/dependabot.yml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
version: 2
2+
updates:
3+
- package-ecosystem: nuget
4+
directory: "/src"
5+
schedule:
6+
interval: daily
7+
open-pull-requests-limit: 10

‎.github/stale.yml‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Number of days of inactivity before an issue becomes stale
2+
daysUntilStale: 7
3+
# Number of days of inactivity before a stale issue is closed
4+
daysUntilClose: 7
5+
# Set to true to ignore issues in a milestone (defaults to false)
6+
exemptMilestones: true
7+
# Comment to post when marking an issue as stale. Set to `false` to disable
8+
markComment: >
9+
This issue has been automatically marked as stale because it has not had
10+
recent activity. It will be closed if no further activity occurs. Thank you
11+
for your contributions.
12+
# Comment to post when closing a stale issue. Set to `false` to disable
13+
closeComment: false
14+
# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
15+
pulls:
16+
daysUntilStale: 30
17+
exemptLabels:
18+
- Question
19+
- Bug
20+
- Feature
21+
- Improvement

‎.github/workflows/merge-dependabot.yml‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
name: merge-dependabot
2+
on:
3+
pull_request:
4+
jobs:
5+
automerge:
6+
runs-on: ubuntu-latest
7+
if: github.actor == 'dependabot[bot]'
8+
steps:
9+
- name: Dependabot Auto Merge
10+
uses: ahmadnassri/[email protected]
11+
with:
12+
target: minor
13+
github-token: ${{ secrets.dependabot }}
14+
command: squash and merge

‎.github/workflows/on-push-do-docs.yml‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
name: on-push-do-docs
2+
on:
3+
push:
4+
jobs:
5+
docs:
6+
runs-on: windows-latest
7+
steps:
8+
- uses: actions/checkout@v4
9+
- name: Run MarkdownSnippets
10+
run: |
11+
dotnet tool install --global MarkdownSnippets.Tool
12+
mdsnippets ${GITHUB_WORKSPACE}
13+
shell: bash
14+
- name: Push changes
15+
run: |
16+
git config --local user.email "[email protected]"
17+
git config --local user.name "GitHub Action"
18+
git commit -m "Docs changes" -a || echo "nothing to commit"
19+
remote="https://${GITHUB_ACTOR}:${{secrets.GITHUB_TOKEN}}@github.com/${GITHUB_REPOSITORY}.git"
20+
branch="${GITHUB_REF:11}"
21+
git push "${remote}" ${branch} || echo "nothing to push"
22+
shell: bash

‎.gitignore‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
*.suo
2+
*.user
3+
bin/
4+
obj/
5+
.vs/
6+
*.DotSettings.user
7+
.idea/
8+
*.received.*
9+
nugets/

0 commit comments

Comments
 (0)