Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions .github/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Code of Conduct

## Our Pledge

We are committed to making participation in this project a harassment-free experience for everyone.

## Our Standards

**Positive behavior:**
- Using welcoming and inclusive language
- Being respectful of differing viewpoints
- Gracefully accepting constructive criticism
- Focusing on what is best for the community

**Unacceptable behavior:**
- Harassment, insults or derogatory comments
- Publishing others' private information
- Any conduct which could reasonably be considered inappropriate

## Enforcement

Violations may be reported to **t.me/kotyarakryt**. All complaints will be reviewed and investigated.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.
38 changes: 38 additions & 0 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Contributing to SimpleKillFeed

Thank you for your interest in contributing! 🎉

## Getting Started

1. Fork the repository
2. Create a new branch: `git checkout -b feature/your-feature`
3. Make your changes
4. Ensure the project builds: `dotnet build`
5. Commit: `git commit -m "feat: add your feature"`
6. Push: `git push origin feature/your-feature`
7. Open a Pull Request

## Commit Convention

We use conventional commits:

| Prefix | Description |
|---|---|
| `feat:` | New feature |
| `fix:` | Bug fix |
| `docs:` | Documentation |
| `chore:` | Maintenance |
| `refactor:` | Code refactoring |

## Code Style

- Follow existing code style
- Add XML doc comments to public methods
- Keep methods small and focused

## Pull Request Requirements

- [ ] Code compiles without errors
- [ ] Changes are tested
- [ ] Documentation is updated if needed
- [ ] PR description clearly explains the changes
36 changes: 36 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
## Description
<!-- What does this PR do? Why is it needed? -->

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update
- [ ] Refactoring
- [ ] Performance improvement

## Related Issue
Closes #

## Changes Made
<!-- List the specific changes made in this PR -->
-
-
-

## Testing
<!-- How did you test your changes? -->
- [ ] Tested on a local CS2 server
- [ ] Tested with multiple players
- [ ] Edge cases considered

## Screenshots
<!-- If applicable, add screenshots or logs -->

## Checklist
- [ ] Code compiles without errors
- [ ] I have tested my changes on a CS2 server
- [ ] I have added/updated XML doc comments
- [ ] I have followed the code style guidelines
- [ ] PR title follows conventional commits format (feat/fix/docs/chore)
- [ ] I have updated README if needed
24 changes: 24 additions & 0 deletions .github/SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Security Policy

## Supported Versions

| Version | Supported |
|---|---|
| Latest | ✅ |
| Older | ❌ |

## Reporting a Vulnerability

If you discover a security vulnerability, please **do NOT open a public issue**.

Instead, contact us privately:
- Telegram: **t.me/kotyarakryt**

We will respond within **48 hours** and work to resolve the issue as quickly as possible.

## What to Include

- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (optional)
Loading