chore: repository cleanup

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,23 @@
+---
+name: Bug report
+about: Create a report to help us improve
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Open scene X
+2. Do Y
+3. See error
+
+**Expected behavior**
+What you expected to happen.
+
+**Environment (please complete the following information):**
+- Unity version: 2020.1.10f1
+- OS: (e.g. Windows 10, macOS 10.15)
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,16 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+---
+
+**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.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+<!-- Describe the change you are making -->
+
+## Changes
+
+- Summary of changes.
+
+## Checklist
+
+- [ ] My change follows the repository's contributing guidelines.
+- [ ] I have run the tests locally (Unity Test Runner).
+
+## Notes
+
+Add any additional notes for reviewers here.

CODE_OF_CONDUCT.md

@@ -0,0 +1,14 @@
+# Contributor Covenant Code of Conduct
+
+Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project a harassment-free experience for everyone.
+
+Standards
+
+Examples of behavior that contributes to a positive environment include:
+
+- Using welcoming and inclusive language.
+- Being respectful of differing viewpoints and experiences.
+
+Unacceptable behavior will not be tolerated. If you experience or witness unacceptable behavior, please open an issue or contact the maintainers.

CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# Contributing
+
+Thanks for considering contributing! A few simple guidelines help maintain a smooth workflow.
+
+How to contribute
+
+1. Fork the repository and create a branch from `main` named `feature/your-topic` or `fix/issue-number`.
+2. Make small, focused commits with clear messages.
+3. Run the tests locally via the Unity Test Runner before opening a PR.
+4. Open a Pull Request describing the change, linking any related issue.
+
+PR checklist
+
+- [ ] Follows existing code style (C# conventions used in Unity projects).
+- [ ] No changes to runtime code that break existing behavior unless necessary and documented.
+- [ ] Tests added or updated for new behavior.
+- [ ] CI checks (if present) pass.
+
+Code style
+
+- Prefer clear, descriptive names for classes and methods.
+- Keep Unity-specific code (Editor-only) inside `#if UNITY_EDITOR` or `Editor` folders.
+
+Reporting issues
+
+Use the issue templates when creating bug reports or feature requests.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Repository contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,14 +1,29 @@
-# Unity-Github-Action
-A repository to showcase github action with Unity. The Unity project is empty.
-Don't forget to change the Unity version in each .yml if you use my files !
+# unity-github-action
 
-This repository has three workflows :
-- "activation.yml" which needs to be executed at the start of your project to get your license and set the "UNITY_LICENSE" variable in github secret. 🔑
-- "test.yml" which verifies for each push that your project run all of its unit tests right, and that the project can be built. ⚙ 
-- "build.yml" which is executed when creating a new release, testing once again your Unity project, and then building it for Windowsx64, and attaching the .zip to your release. 🔨
+This repository contains a minimal Unity project used as an example for GitHub Actions / CI workflows.
 
-Thanks to @webbertaken ( https://game.ci/ )
+Unity version
 
-Tutorials I used :
-https://isaacbroyles.com/gamedev/2020/07/04/unity-github-actions.html
-https://bearandhammer.net/2020/06/13/github-actions-unity-3d/
+- Editor: 2020.1.10f1
+
+Contents
+
+- `Assets/` — Scenes, scripts and tests.
+- `ProjectSettings/` — Unity project settings.
+
+Getting started
+
+1. Open this folder in Unity Editor 2020.1.10f1.
+2. Open `Assets/Scenes/SampleScene.unity` and press Play.
+
+Running tests
+
+Use Unity Test Runner (Window → General → Test Runner) to run the tests in `Assets/Tests`.
+
+Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+License
+
+This project is licensed under the MIT License. See [LICENSE](LICENSE).