mirror of
https://github.com/celisej567/BCWSsrc.git
synced 2026-02-25 14:37:04 +03:00
Delete .github directory
This commit is contained in:
celisej567
GitHub
43
.github/CONTRIBUTING.md
vendored
43
.github/CONTRIBUTING.md
vendored
@@ -1,43 +0,0 @@
|
||||
This file details how to contribute to the Mapbase project on GitHub:
|
||||
https://github.com/mapbase-source/source-sdk-2013
|
||||
|
||||
For the original Source SDK 2013 contribution guidelines, click here:
|
||||
https://github.com/ValveSoftware/source-sdk-2013/blob/master/CONTRIBUTING
|
||||
|
||||
---
|
||||
|
||||
Mapbase is a project which many Source modders draw from, so it has its own unique standards
|
||||
for contributions which differ from other projects, but it is still an open-source repository
|
||||
that is always open to contributions.
|
||||
|
||||
Whenever you contribute to the Mapbase repository, you must keep in mind that any contributions
|
||||
made could be deployed to all mods utilizing Mapbase, which can include everything from high-profile
|
||||
Steam mods to amateur HL2 maps. Many contributions can also end up being available in both SP and MP
|
||||
if the contributions are not obviously exclusive to one of the two.
|
||||
|
||||
All contributions must follow the following rules:
|
||||
|
||||
* A contribution must be aligned with Mapbase's goals and priorities and should not be "subjective"
|
||||
or related to a specific mod or type of mod. For example, fixing an existing issue or adding a
|
||||
new tool for mappers to use is usually fine, but adding a new custom weapon with its own assets
|
||||
is usually not fit for Mapbase.
|
||||
|
||||
* All content in a contribution must be either already legally open-source or done with the
|
||||
full permission of the content's original creator(s).
|
||||
|
||||
* Contributions must not break existing maps/content or interfere with them in a negative or non-objective way.
|
||||
|
||||
* Code contributions are not obliged to follow Mapbase's preprocessor conventions (e.g. #ifdef MAPBASE),
|
||||
although following them is usually acceptable.
|
||||
|
||||
* If you are contributing a file you created yourself specifically for Mapbase, you are required to
|
||||
use the custom "Mapbase - Source 2013" header used in other Mapbase files as of Mapbase v5.0.
|
||||
You are encouraged to append an "Author(s)" part to that header in your file in order to clarify who wrote it.
|
||||
|
||||
If your contribution is accepted, you may be listed in Mapbase's credits and the README's external content list:
|
||||
https://github.com/mapbase-source/source-sdk-2013/wiki/Mapbase-Credits#Contributors
|
||||
https://github.com/mapbase-source/source-sdk-2013/blob/master/README
|
||||
|
||||
You may also receive the "Contributor" or "Major Contributor" role on Mapbase's Discord server if you are
|
||||
a member of it.
|
||||
|
||||
25
.github/ISSUE_TEMPLATE/bug-report---code.md
vendored
25
.github/ISSUE_TEMPLATE/bug-report---code.md
vendored
@@ -1,25 +0,0 @@
|
||||
---
|
||||
name: Bug report - Code
|
||||
about: Create a bug report related to the source code itself. (e.g. a compile error)
|
||||
title: "[CODE] "
|
||||
labels: Bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Describe the bug
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
### Steps to reproduce
|
||||
Steps to reproduce the behavior:
|
||||
1. Have '...' set to something
|
||||
2. ???
|
||||
3. See error
|
||||
|
||||
### Expected behavior
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
---
|
||||
|
||||
### Additional context
|
||||
(Optional) Add any other context about the problem here.
|
||||
25
.github/ISSUE_TEMPLATE/bug-report---game.md
vendored
25
.github/ISSUE_TEMPLATE/bug-report---game.md
vendored
@@ -1,25 +0,0 @@
|
||||
---
|
||||
name: Bug report - Game
|
||||
about: Create a bug report related to game behavior.
|
||||
title: "[GAME] "
|
||||
labels: Bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Describe the bug
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
### Steps to reproduce
|
||||
Steps to reproduce the behavior:
|
||||
1. Have '...' in the map
|
||||
2. ???
|
||||
3. See error
|
||||
|
||||
### Expected behavior
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
---
|
||||
|
||||
### Additional context
|
||||
(Optional) Add any other context about the problem here.
|
||||
25
.github/ISSUE_TEMPLATE/bug-report---misc.md
vendored
25
.github/ISSUE_TEMPLATE/bug-report---misc.md
vendored
@@ -1,25 +0,0 @@
|
||||
---
|
||||
name: Bug report - Miscellaneous
|
||||
about: Create a bug report not related to any of the other subjects.
|
||||
title: "[MISC] "
|
||||
labels: Bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Describe the bug
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
### Steps to reproduce
|
||||
Steps to reproduce the behavior:
|
||||
1. Do '...'
|
||||
2. ???
|
||||
3. See error
|
||||
|
||||
### Expected behavior
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
---
|
||||
|
||||
### Additional context
|
||||
(Optional) Add any other context about the problem here.
|
||||
25
.github/ISSUE_TEMPLATE/bug-report---npc.md
vendored
25
.github/ISSUE_TEMPLATE/bug-report---npc.md
vendored
@@ -1,25 +0,0 @@
|
||||
---
|
||||
name: Bug report - NPCs
|
||||
about: Create a bug report related to NPCs.
|
||||
title: "[NPCs] "
|
||||
labels: Bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Describe the bug
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
### Steps to reproduce
|
||||
Steps to reproduce the behavior:
|
||||
1. Have '...' do something
|
||||
2. ???
|
||||
3. See error
|
||||
|
||||
### Expected behavior
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
---
|
||||
|
||||
### Additional context
|
||||
(Optional) Add any other context about the problem here.
|
||||
25
.github/ISSUE_TEMPLATE/bug-report---tools.md
vendored
25
.github/ISSUE_TEMPLATE/bug-report---tools.md
vendored
@@ -1,25 +0,0 @@
|
||||
---
|
||||
name: Bug report - Tools
|
||||
about: Create a bug report related to compile tools, editor stuff, etc.
|
||||
title: "[TOOLS] "
|
||||
labels: Bug, Tools
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Describe the bug
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
### Steps to reproduce
|
||||
Steps to reproduce the behavior:
|
||||
1. Have '...' in the map
|
||||
2. ???
|
||||
3. See error
|
||||
|
||||
### Expected behavior
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
---
|
||||
|
||||
### Additional context
|
||||
(Optional) Add any other context about the problem here.
|
||||
@@ -1,29 +0,0 @@
|
||||
---
|
||||
name: Bug report - Visuals/Graphics
|
||||
about: Create a bug report related to visual issues. (e.g. shaders, projected textures,
|
||||
etc.)
|
||||
title: "[VISUAL] "
|
||||
labels: Bug
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Describe the bug
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
### Steps to reproduce
|
||||
Steps to reproduce the behavior:
|
||||
1. Have '...' in the map
|
||||
2. ???
|
||||
3. See error
|
||||
|
||||
### Expected behavior
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
### Media
|
||||
Any related screenshots, videos, etc. which show the bug.
|
||||
|
||||
---
|
||||
|
||||
### Additional context
|
||||
(Optional) Add any other context about the problem here.
|
||||
25
.github/ISSUE_TEMPLATE/bug-report---vscript.md
vendored
25
.github/ISSUE_TEMPLATE/bug-report---vscript.md
vendored
@@ -1,25 +0,0 @@
|
||||
---
|
||||
name: Bug report - VScript
|
||||
about: Create a bug report related to VScript.
|
||||
title: "[VSCRIPT] "
|
||||
labels: Bug, VScript
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Describe the bug
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
### Steps to reproduce
|
||||
Steps to reproduce the behavior:
|
||||
1. Have '...' in the script
|
||||
2. ???
|
||||
3. See error
|
||||
|
||||
### Expected behavior
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
---
|
||||
|
||||
### Additional context
|
||||
(Optional) Add any other context about the problem here.
|
||||
22
.github/ISSUE_TEMPLATE/feature-request---code.md
vendored
22
.github/ISSUE_TEMPLATE/feature-request---code.md
vendored
@@ -1,22 +0,0 @@
|
||||
---
|
||||
name: Feature request - Code
|
||||
about: Suggest an idea related to the source code itself. (e.g. a new utility function)
|
||||
title: "[CODE] "
|
||||
labels: Enhancement
|
||||
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
|
||||
(Optional) Add any other context or screenshots about the feature request here.
|
||||
22
.github/ISSUE_TEMPLATE/feature-request---game.md
vendored
22
.github/ISSUE_TEMPLATE/feature-request---game.md
vendored
@@ -1,22 +0,0 @@
|
||||
---
|
||||
name: Feature request - Game
|
||||
about: Suggest an idea related to game behavior.
|
||||
title: "[GAME] "
|
||||
labels: Enhancement
|
||||
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
|
||||
(Optional) Add any other context or screenshots about the feature request here.
|
||||
22
.github/ISSUE_TEMPLATE/feature-request---misc.md
vendored
22
.github/ISSUE_TEMPLATE/feature-request---misc.md
vendored
@@ -1,22 +0,0 @@
|
||||
---
|
||||
name: Feature request - Miscellaneous
|
||||
about: Suggest an idea not related to any of the other subjects.
|
||||
title: "[MISC] "
|
||||
labels: Enhancement
|
||||
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
|
||||
(Optional) Add any other context or screenshots about the feature request here.
|
||||
22
.github/ISSUE_TEMPLATE/feature-request---npc.md
vendored
22
.github/ISSUE_TEMPLATE/feature-request---npc.md
vendored
@@ -1,22 +0,0 @@
|
||||
---
|
||||
name: Feature request - NPCs
|
||||
about: Suggest an idea related to NPCs.
|
||||
title: "[NPCs] "
|
||||
labels: Enhancement
|
||||
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
|
||||
(Optional) Add any other context or screenshots about the feature request here.
|
||||
@@ -1,22 +0,0 @@
|
||||
---
|
||||
name: Feature request - Tools
|
||||
about: Suggest an idea related to compile tools, editor stuff, etc.
|
||||
title: "[TOOLS] "
|
||||
labels: Enhancement, Tools
|
||||
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
|
||||
(Optional) Add any other context or screenshots about the feature request here.
|
||||
@@ -1,23 +0,0 @@
|
||||
---
|
||||
name: Feature request - Visuals/Graphics
|
||||
about: Suggest an idea related to visuals or graphics. (e.g. shaders, projected textures,
|
||||
etc.)
|
||||
title: "[VISUAL] "
|
||||
labels: Enhancement
|
||||
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
|
||||
(Optional) Add any other context or screenshots about the feature request here.
|
||||
@@ -1,22 +0,0 @@
|
||||
---
|
||||
name: Feature request - VScript
|
||||
about: Suggest an idea related to VScript.
|
||||
title: "[VSCRIPT] "
|
||||
labels: Enhancement, VScript
|
||||
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
|
||||
(Optional) Add any other context or screenshots about the feature request here.
|
||||
11
.github/pull-request-template.md
vendored
11
.github/pull-request-template.md
vendored
@@ -1,11 +0,0 @@
|
||||
(Describe your PR here and then fill out the checklist at the bottom)
|
||||
|
||||
---
|
||||
|
||||
#### Does this PR close any issues?
|
||||
* (Optional) Insert issue number(s) and any related info here
|
||||
|
||||
<!-- Replace [ ] with [x] for each item your PR satisfies -->
|
||||
#### PR Checklist
|
||||
- [ ] **My PR follows all guidelines in the CONTRIBUTING.md file**
|
||||
- [ ] My PR targets a `develop` branch OR targets another branch with a specific goal in mind
|
||||
Reference in New Issue
Block a user