Skip to content

Commit

Permalink
Add project files.
Browse files Browse the repository at this point in the history
  • Loading branch information
AptiviCEO committed Oct 15, 2023
0 parents commit 0e172da
Show file tree
Hide file tree
Showing 72 changed files with 5,134 additions and 0 deletions.
29 changes: 29 additions & 0 deletions .editorconfig
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
root = true

[*]
end_of_line = crlf
insert_final_newline = true
indent_style = space
indent_size = 4

# IDE0060: Remove unused parameter
dotnet_diagnostic.IDE0060.severity = warning
dotnet_diagnostic.CA1822.severity = none

[*.md]
charset = utf-8

[*.sh]
end_of_line = lf

[*.resx]
end_of_line = crlf
insert_final_newline = true
indent_style = space
indent_size = 2

[*.csproj]
end_of_line = crlf
insert_final_newline = true
indent_style = space
indent_size = 2
63 changes: 63 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
###############################################################################
# Set default behavior to automatically normalize line endings.
###############################################################################
* text=auto

###############################################################################
# Set default behavior for command prompt diff.
#
# This is need for earlier builds of msysgit that does not have it on by
# default for csharp files.
# Note: This is only used by command line
###############################################################################
#*.cs diff=csharp

###############################################################################
# Set the merge driver for project and solution files
#
# Merging from the command prompt will add diff markers to the files if there
# are conflicts (Merging from VS is not affected by the settings below, in VS
# the diff markers are never inserted). Diff markers may cause the following
# file extensions to fail to load in VS. An alternative would be to treat
# these files as binary and thus will always conflict and require user
# intervention with every merge. To do so, just uncomment the entries below
###############################################################################
#*.sln merge=binary
#*.csproj merge=binary
#*.vbproj merge=binary
#*.vcxproj merge=binary
#*.vcproj merge=binary
#*.dbproj merge=binary
#*.fsproj merge=binary
#*.lsproj merge=binary
#*.wixproj merge=binary
#*.modelproj merge=binary
#*.sqlproj merge=binary
#*.wwaproj merge=binary

###############################################################################
# behavior for image files
#
# image files are treated as binary by default.
###############################################################################
#*.jpg binary
#*.png binary
#*.gif binary

###############################################################################
# diff behavior for common document formats
#
# Convert binary document formats to text before diffing them. This feature
# is only available from the command line. Turn it on by uncommenting the
# entries below.
###############################################################################
#*.doc diff=astextplain
#*.DOC diff=astextplain
#*.docx diff=astextplain
#*.DOCX diff=astextplain
#*.dot diff=astextplain
#*.DOT diff=astextplain
#*.pdf diff=astextplain
#*.PDF diff=astextplain
#*.rtf diff=astextplain
#*.RTF diff=astextplain
16 changes: 16 additions & 0 deletions .github/ISSUE_TEMPLATE/ask-a-question.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
name: Ask a question
about: Ask us anything about SpecProbe.
title: "[Q&A] [FeatureName] - [Question]"
labels: ''
assignees: ''

---

### -+--> Type of question
- [ ] General
- [ ] Parser
- [ ] Hardware
- [ ] Others

### -+--> Ask here
43 changes: 43 additions & 0 deletions .github/ISSUE_TEMPLATE/report-an-issue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
name: Report an issue
about: Thank you for reporting a bug to us.
title: "[BUG] [featureName] - [issue]"
labels: ''
assignees: ''

---

### -+--> Description

<!-- Describe how this bug happened, and general information about it. Note that we only speak Arabic and English, so if you're on any other language than we know, then translate. -->
<!-- Note that you need to be as more descriptive as you can so we can understand this bug. -->


### -+--> Expected behavior

<!-- How do you expect SpecProbe to behave on the suspected component. -->


### -+--> Actual behavior

<!-- What did the suspected component do instead? -->


### -+--> Steps to reproduce

<!-- Provide clear step-by-step instructions on how do you reporduce this bug. -->
1.
1.
1.

### -+--> System Information

<!-- This is here in case it's a hardware probing problem, but the probing should work normally. -->
- **OS:**
- **CPU:**
- **RAM:**
- **HDD:**

### -+--> Version (include commit number if applicable)

<!-- This should be in this format: <Version> (<Commit>) (<Branch>). Commit number and branch required for development builds. -->
18 changes: 18 additions & 0 deletions .github/ISSUE_TEMPLATE/request-a-feature.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
name: Request a feature
about: Suggest an idea to us.
title: "[ADD] [FeatureName] - [Feature]"
labels: ''
assignees: ''

---

### -+--> Description of new feature
<!--- Explain about a new feature here. --->


### -+--> What does it add?
- [ ] New hardware category
- [ ] Others

### -+--> Have you tried doing it?
38 changes: 38 additions & 0 deletions .github/issue_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
### -+--> Description

<!-- Describe how this bug happened, and general information about it. Note that we only speak Arabic and English, so if you're on any other language than we know, then translate. -->
<!-- Note that you need to be as more descriptive as you can so we can understand this bug. -->


### -+--> Expected behavior

<!-- How do you expect SpecProbe to behave on the suspected component. -->


### -+--> Actual behavior

<!-- What did the suspected component do instead? -->


### -+--> Steps to reproduce

<!-- Provide clear step-by-step instructions on how do you reporduce this bug. -->
1.
1.
1.

### -+--> System Information

<!-- This is here in case it's a hardware probing problem, but the probing should work normally. -->
**OS:**

**CPU:**

**RAM:**

**HDD:**

### -+--> Version (include commit number if applicable)

<!-- This should be in this format: <Version> (<Commit>). Commit number required for development builds. -->

20 changes: 20 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
## Description
<!-- Describe about your pull request. Note that you need to be as more descriptive as you can so we can understand this request. -->


## Change type
<!-- Specify what kind of changes you made. -->
- [ ] Bug fixes
- [ ] Performance improvements
- [ ] Feature changes
- [ ] Behavioral changes
- [ ] Other (specify)

## Tested?
<!-- Have you tested your changes? -->
- [ ] Yes, I have
- [ ] No, I haven't
- [ ] Not sure

## Specify other changes
<!-- Specify the changes that wouldn't fit into the selection. -->
47 changes: 47 additions & 0 deletions .github/workflows/build-linux.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
name: Build Project (Linux)

on:
push:
branches:
- main
pull_request:
branches:
- main

jobs:
build:

runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v3
with:
ref: ${{ github.ref }}
- name: Setup .NET 6.0
uses: actions/setup-dotnet@v3
with:
dotnet-version: '6.0.x'
- name: Solution Compilation
run: dotnet build --configuration Debug
- name: Testing
run: dotnet test --configuration Debug
- uses: actions/upload-artifact@v3
if: success() || failure()
with:
name: sp-build
path: "SpecProbe.Bin/"

notify:

runs-on: ubuntu-latest
needs:
- build
if: ${{ always() }}

steps:
- name: Notify
uses: nobrayner/discord-webhook@v1
with:
github-token: ${{ secrets.G_TOKEN }}
discord-webhook: ${{ secrets.DISCORD_WEBHOOK }}

47 changes: 47 additions & 0 deletions .github/workflows/build-macos.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
name: Build Project (macOS)

on:
push:
branches:
- main
pull_request:
branches:
- main

jobs:
build:

runs-on: macos-latest

steps:
- uses: actions/checkout@v3
with:
ref: ${{ github.ref }}
- name: Setup .NET 6.0
uses: actions/setup-dotnet@v3
with:
dotnet-version: '6.0.x'
- name: Solution Compilation
run: dotnet build --configuration Debug
- name: Testing
run: dotnet test --configuration Debug
- uses: actions/upload-artifact@v3
if: success() || failure()
with:
name: sp-build
path: "SpecProbe.Bin/"

notify:

runs-on: ubuntu-latest
needs:
- build
if: ${{ always() }}

steps:
- name: Notify
uses: nobrayner/discord-webhook@v1
with:
github-token: ${{ secrets.G_TOKEN }}
discord-webhook: ${{ secrets.DISCORD_WEBHOOK }}

47 changes: 47 additions & 0 deletions .github/workflows/build-win.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
name: Build Project (Windows)

on:
push:
branches:
- main
pull_request:
branches:
- main

jobs:
build:

runs-on: windows-latest

steps:
- uses: actions/checkout@v3
with:
ref: ${{ github.ref }}
- name: Setup .NET 6.0
uses: actions/setup-dotnet@v3
with:
dotnet-version: '6.0.x'
- name: Solution Compilation
run: dotnet build --configuration Debug
- name: Testing
run: dotnet test --configuration Debug
- uses: actions/upload-artifact@v3
if: success() || failure()
with:
name: sp-build
path: "SpecProbe.Bin/"

notify:

runs-on: ubuntu-latest
needs:
- build
if: ${{ always() }}

steps:
- name: Notify
uses: nobrayner/discord-webhook@v1
with:
github-token: ${{ secrets.G_TOKEN }}
discord-webhook: ${{ secrets.DISCORD_WEBHOOK }}

Loading

0 comments on commit 0e172da

Please sign in to comment.