1
0
mirror of https://github.com/tommytran732/Pterodactyl-Script synced 2024-10-18 04:35:12 -04:00

Remove legacy workflows

Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2022-12-07 12:04:19 -05:00
parent e8b156bf44
commit e70b7152a8
No known key found for this signature in database
GPG Key ID: 060B29EB996BD9F2
2 changed files with 0 additions and 57 deletions

View File

@ -1,33 +0,0 @@
**Note: for support questions, please use the [Discord](https://revenact.io/discord)**. This repository's issues are reserved for feature requests and bug reports.
* **I'm submitting a ...**
- [ ] Bug Report
- [ ] Feature Request
- [ ] Support Request => Please do not submit support request here, see note at the top of this template.
* **Do you want to request a *feature* or report a *bug*?**
* **[Pastebin](https://pastebin.com) link of the error**
* **What is the expected behavior?**
* **What is the motivation / use case for changing the behavior?**
* **Please tell us about your environment:**
```
- Version: vX.X.X
- OS: [all | Ubuntu XX.XX | Debian XX | CentOS XX | Fedora XX | RedHat XX ]
- Install Options: [1-22 | Apache, Nginx | Theme ]
```
* **Other information** (e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

View File

@ -1,24 +0,0 @@
* **Please check if the PR fulfills these requirements**
- [ ] The commit message follows our [guidelines](https://github.com/Revenact/Pterodactyl-Script/blob/master/CONTRIBUTING.md)
- [ ] Tests have been made.
- [ ] [Readme](https://github.com/Revenact/Pterodactyl-Script/blob/master/README.md) have been updated (for bug fixes / features)
- [ ] [Changelog](https://github.com/Revenact/Pterodactyl-Script/blob/master/CHANGELOG.md) has be updated, and a version made
* **What kind of change does this PR introduce?** (Bug fix, feature, OS support, ...)
* **What is the current behavior?** (You can also link to an open issue here)
* **What is the new behavior (if this is a feature change)?**
* **Does this PR introduce a breaking change?** (What changes might users need to make in their application due to this PR?)
* **Other information**: