Skip to content

Commit

Permalink
Merge pull request Helixis#1 from tgstation/master
Browse files Browse the repository at this point in the history
Master
  • Loading branch information
Helixis authored Sep 26, 2020
2 parents 65e19d7 + a8266d0 commit bc7d3f7
Show file tree
Hide file tree
Showing 874 changed files with 118,912 additions and 35,637 deletions.
17 changes: 3 additions & 14 deletions .codecov.yml
Original file line number Diff line number Diff line change
@@ -1,20 +1,9 @@
codecov:
strict_yaml_branch: master
coverage:
status:
project:
default:
threshold: 0
if_no_uploads: failure
if_ci_failed: failure
patch:
default:
target: 100
only_pulls: true
changes:
default:
if_no_uploads: failure
if_ci_failed: failure
only_pulls: yes
target: auto
threshold: 3%
patch: off
comment:
layout: "header, diff, changes"
34 changes: 34 additions & 0 deletions .dockerignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
*/bin
*/obj

.git
.github
.vs
.vscode
.codecov.yml
.dockerignore
.gitignore
.travis.yml
appveyor.yml
omnisharp.json
README.md

build/**
!build/analyzers.ruleset
!build/tgs.docker.sh
!build/tgs.ico
!build/tgs.png
!build/stylecop.json
!build/Version.props
docs
src/DMAPI
src/Tgstation.Server.Host/ClientApp/build
src/Tgstation.Server.Host/ClientApp/node_modules
src/Tgstation.Server.Host/wwwroot
src/Tgstation.Server.Host/appsettings.Development.json
src/Tgstation.Server.Host/tgs.bat
src/Tgstation.Server.Host/tgs.sh
src/Tgstation.Server.Host.Client
src/Tgstation.Server.Host.Service
tests
tools
16 changes: 16 additions & 0 deletions .editorconfig
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
[*]
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
[*.cs]
indent_style = tab
indent_size = 4
[*.csproj]
indent_style = space
indent_size = 2
[*.dm]
indent_style = tab
indent_size = 4
[*.yml]
indent_style = space
indent_size = 2
2 changes: 1 addition & 1 deletion .github/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at #coderbus on irc.rizon.net:6667. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at the [#coderbus discord](https://discord.gg/Vh8TJp9). The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Expand Down
212 changes: 159 additions & 53 deletions .github/CONTRIBUTING.md

Large diffs are not rendered by default.

7 changes: 0 additions & 7 deletions .github/ISSUE_TEMPLATE.md

This file was deleted.

37 changes: 37 additions & 0 deletions .github/ISSUE_TEMPLATE/bug-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
---
name: Bug Report
about: Report a problem with the server
title: ''
labels: Bug, Reproduction Required
assignees: Cyberboss

---

**Describe the bug**
A clear and concise description of what the bug is. Please note that client issues (i.e. Control panel crashes) do not belong in this repo and should be report in their own.

**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.

**Logs**
Please include full server logs to help diagnose your problem

**Server State: (please complete the following information):**
- OS:
- Version:
- Database Type/Version:
- BYOND Version Used:
- git Repository Used:
- Origin Commit hash Used:
- Active Test Merges:
- Client Version:

**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 the server
title: ''
labels: Feature Request, Backlog
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.
21 changes: 21 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
[Base Branch]: # (Please set the base branch of your pull request appropriately. If you only made a patch, code improvement, non-server code change, or comment/documentation update please target the `master` branch. Otherwise, target the `dev` branch.)

[Release Notes]: # (Your PR should contain a detailed list of notable changes, titled appropriately. This includes any observable changes to the server or DMAPI. See examples below.)

:cl:
Description of your change.
Each newline corresponds to a release note in the release your change is included in.
/:cl:

:cl:
You can also have multiple sets of release notes per pull request.
They will be amalgamated together in the end.
/:cl:

:cl: Categories
Categories are divided up in the release notes and set after the :cl: header.
The default category is Core.
The current standard categories are Core, DMAPI, HTTP API, and Host Watchdog.
/:cl:

[Why]: # (If this does not close or work on an existing GitHub issue, please add a short description [two lines down] of why you think these changes would benefit the server. If you can't justify it in words, it might not be worth adding.)
15 changes: 15 additions & 0 deletions .github/workflows/artifact-cleanup.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
name: 'Delete Old Artifacts'
on:
schedule:
- cron: '0 0 * * *' # every day

jobs:
delete-artifacts:
name: Delete Artifacts
runs-on: ubuntu-latest
steps:
- name: Delete Artifacts
uses: kolpav/purge-artifacts-action@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
expire-in: 30days # Setting this to 0 will delete all artifacts
Loading

0 comments on commit bc7d3f7

Please sign in to comment.