Skip to content

Align repository with Kovina Repository Standard #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sparshsam merged 1 commit into from
Jun 30, 2026
Merged

Align repository with Kovina Repository Standard #20

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
44 changes: 8 additions & 36 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,39 +1,11 @@
# Contributing
# Contributing to HissTastic

Thank you for considering a contribution.
Please see [docs/Contributing.md](docs/Contributing.md) for the full contributing guide.

## Scope
## Quick Links
- [Development Setup](docs/Development.md)
- [Architecture](docs/Architecture.md)
- [Deployment](docs/Deployment.md)
- [Testing](docs/Testing.md)

This repository is currently a preserved legacy prototype. Contributions should focus on documentation, preservation quality, compatibility fixes, and clearly scoped modernization work.

Do not rewrite gameplay, change mechanics, or add new features unless the change is explicitly part of an approved modernization task.

## Process

1. Fork the repository.
2. Create a feature branch such as `docs/readme-alignment` or `fix/asset-loading`.
3. Make focused changes.
4. Run the relevant verification steps.
5. Submit a pull request with a short summary and manual test notes.

## Git Safety

- Never force-push `main`.
- Never rewrite protected or shared branches.
- Prefer normal `git push` after commits.
- Force-push only on isolated feature branches when absolutely necessary.
- If a force-push is used, explain the reason in the pull request or final report.

## Standards

- Preserve the original prototype unless a change is explicitly requested.
- Keep documentation restrained and accurate.
- Avoid telemetry, engagement-pressure mechanics, or unnecessary network services.
- Document any change that affects runtime behavior, dependencies, or data handling.
- Preserve deterministic replay behavior when changing input, spawn, timing, or scoring code.
- Keep ghost racing local-only and non-scoring.
- Follow the [ecosystem standards](https://github.com/sparshsam/ecosystem-standards).

## Code of Conduct

This project follows the [Code of Conduct](CODE_OF_CONDUCT.md).
By contributing, you agree that your contributions will be licensed under MIT.
Loading
Loading