To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Il s'agit d'une implémentation en terminal du jeu **Puissance 4**, où deux joueurs peuvent s'affronter sur une grille pour aligner quatre pièces horizontalement, verticalement ou diagonalement. Le jeu propose trois modes :
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-**Mode 1** : Jeu à deux joueurs (humain contre humain).
-**Mode 2** : Jeu en solo contre une IA aléatoire.
-**Mode 3** : Jeu en solo contre une IA intelligente.
## Add your files
Le jeu est affiché à l'aide de l'ASCII art dans le terminal.
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
## Prérequis
-[ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
Avant de lancer l'application, vous devez avoir les éléments suivants installés :
-[ ] [Set up project integrations](https://gitedu.hesge.ch/anthony.bouillan/puissance4/-/settings/integrations)
Assurez-vous que ces outils sont disponibles sur votre système.
## Collaborate with your team
## Installation
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
Pour installer et lancer le jeu, suivez ces étapes :
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
2. Compilez le projet :
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
```sh
make
```
# Editing this README
3. Exécutez le jeu :
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
```sh
./puissance4
```
## Suggestions for a good README
Le jeu s'affichera dans votre terminal.
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Utilisation
## Name
Lorsque vous lancez le jeu, vous serez invité à choisir un mode de jeu et à commencer à jouer. Vous devrez entrer les colonnes où vous souhaitez placer vos pions.
Choose a self-explaining name for your project.
## Description
## Contribuer
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
Les contributions sont les bienvenues ! Voici comment vous pouvez contribuer au projet :
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
1. Forkez le projet
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
2. Créez votre branche de fonctionnalité (`git checkout -b fonctionnalite/nom-de-la-fonctionnalite`)
3. Commitez vos modifications (`git commit -m 'Ajout de la fonctionnalité nom-de-la-fonctionnalite'`)
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
### Mode à deux joueurs
Jouez à Puissance 4 avec un autre joueur sur le même appareil.
### Mode solo contre IA aléatoire
Affrontez une IA qui place ses pions de manière aléatoire.
### Mode solo contre IA intelligente
Affrontez une IA qui utilise une logique de jeu plus avancée pour décider de ses mouvements.
## Usage
### Affichage ASCII
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Le jeu est affiché dans le terminal à l'aide d'ASCII art, offrant une expérience simple et agréable.
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
## Docs
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
Le dossier **docs** contient un petit fichier d'analyse, ainsi que le cahier des charges du projet.
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
## Commandes Make disponibles
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Voici les commandes `make` disponibles dans le projet :
## Authors and acknowledgment
-**`make`** ou **`make puissance4`** : Compile le jeu.
Show your appreciation to those who have contributed to the project.
-**`make test_puissance4`** : Compile et lance les tests unitaires pour le projet.
-**`make clean`** : Supprime les fichiers générés (binaires, objets, etc.).
-**`make run`** : Lance le jeu avec des paramètres spécifiques (ex. `./puissance4 3 5 6`).
-**`make run_unit_tests`** : Exécute les tests unitaires.
-**`make run_all_tests`** : Exécute les tests unitaires et les testbeds.
-**`make tests`** : Compile et lance uniquement les testbeds.
## License
## Licence
For open source projects, say how it is licensed.
## Project status
Ce projet est sous licence MIT. Voir le fichier [LICENSE](LICENSE) pour plus de détails.
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
