Skip to content

Commit fbec9ba

Browse files
authored
Initial commit
0 parents  commit fbec9ba

File tree

13 files changed

+745
-0
lines changed

13 files changed

+745
-0
lines changed

.editorconfig

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# This file should only include settings that affect the physical contents of the file, not just how it appears in an editor.
2+
# Do not include personal preference presentation settings like a tab's `indent_size` in this file; those should be specified
3+
# in a parent .editorconfig file outside of the repository.
4+
# v1.7
5+
6+
# Ensure that personal preference presentation settings can be inherited from parent .editorconfig files.
7+
root = false
8+
9+
#### Core EditorConfig Options ####
10+
11+
[*]
12+
charset = utf-8
13+
indent_style = tab
14+
end_of_line = crlf
15+
insert_final_newline = true
16+
trim_trailing_whitespace = true
17+
18+
# For some languages, the number of spaces used for indentation matters.
19+
[*.{tf,md,psd1,pp,yml,yaml}]
20+
indent_style = space
21+
indent_size = 2
22+
23+
24+
#### .NET Coding Conventions ####
25+
26+
csharp_style_namespace_declarations = file_scoped

.gitattributes

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
# Use 'git add --renormalize .' to apply rules to files added to the repository before the .gitattributes file.
2+
3+
# Have GitHub language statistics ignore generated files.
4+
# More info: https://github.com/github-linguist/linguist/blob/master/docs/overrides.md
5+
#generatedFiles/** linguist-generated=true
6+
7+
# Auto detect text files and perform LF normalization.
8+
* text=auto
9+
10+
# Documents
11+
*.doc diff=astextplain
12+
*.DOC diff=astextplain
13+
*.docx diff=astextplain
14+
*.DOCX diff=astextplain
15+
*.dot diff=astextplain
16+
*.DOT diff=astextplain
17+
*.pdf diff=astextplain
18+
*.PDF diff=astextplain
19+
*.rtf diff=astextplain
20+
*.RTF diff=astextplain
21+
*.md text
22+
*.adoc text
23+
*.textile text
24+
*.mustache text
25+
*.csv text
26+
*.tab text
27+
*.tsv text
28+
*.sql text
29+
30+
# Graphics
31+
*.png binary
32+
*.jpg binary
33+
*.jpeg binary
34+
*.gif binary
35+
*.tif binary
36+
*.tiff binary
37+
*.ico binary
38+
# SVG treated as an asset (binary) by default, but it's actually just a text file so let's treat it as one.
39+
#*.svg binary
40+
*.svg text
41+
*.eps binary

.github/CODEOWNERS

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Auto-include these teams/individuals on all PRs.
2+
* @deadlydog

.github/FUNDING.yml

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# These are supported funding model platforms
2+
3+
github: deadlydog # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
4+
patreon: # Replace with a single Patreon username
5+
open_collective: # Replace with a single Open Collective username
6+
ko_fi: # Replace with a single Ko-fi username
7+
tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
8+
community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
9+
liberapay: # Replace with a single Liberapay username
10+
issuehunt: # Replace with a single IssueHunt username
11+
otechie: # Replace with a single Otechie username
12+
custom: https://www.paypal.me/deadlydogDan # Replace with a single custom sponsorship URL

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: 'Bug: '
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### Describe the bug
11+
12+
A clear and concise description of what the bug is.
13+
14+
### To reproduce
15+
16+
Steps to reproduce the behavior:
17+
18+
1. Go to '...'
19+
2. Click on '....'
20+
3. Scroll down to '....'
21+
4. See error
22+
23+
### Expected behavior
24+
25+
A clear and concise description of what you expected to happen.
26+
27+
### Screenshots
28+
29+
If applicable, add screenshots or video to help explain your problem.
30+
31+
### System information
32+
33+
- Device: (e.g. PC, iPhone6)
34+
- OS: (e.g. Windows 10, iOS)
35+
- Browser (e.g. Chrome, Safari)
36+
- Version (e.g. 22)
37+
38+
### Additional context
39+
40+
Add any other context or information about the problem here.
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: 'Feature Request: '
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### Is your feature request related to a problem? Please describe
11+
12+
A clear and concise description of what the problem is. Ex. I'm always frustrated when '...'. Ex. I want to be able to '...'.
13+
14+
### Describe the solution you'd like
15+
16+
A clear and concise description of what you want to happen.
17+
18+
### Describe alternatives you've considered
19+
20+
A clear and concise description of any alternative solutions or features you've considered.
21+
22+
### Additional context
23+
24+
Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
### Summary
2+
3+
A brief summary of the change this PR brings.
4+
5+
### Checklist
6+
7+
Addresses issue #ISSUE_NUMBER (if applicable)
8+
9+
- [ ] Tests have been added for this code change (if applicable)
10+
- [ ] Docs have been added or updated (if applicable)
11+
- [ ] Code format follows the project style
12+
- [ ] All new and existing tests passed
13+
14+
### What type of changes does this PR include
15+
16+
- [ ] Bug fix (non-breaking change which fixes an issue)
17+
- [ ] New feature (non-breaking change which adds functionality)
18+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
19+
20+
### Describe the change
21+
22+
What is the motivation for this change? What does it do? What problem does it solve?
23+
24+
### Additional information
25+
26+
Any other information about the change, such as screenshots, example flows, etc.

0 commit comments

Comments
 (0)