Repository: incentive-factory/iletaitunefoisundev Branch: develop Commit: d6d6679b6e03 Files: 21 Total size: 62.1 KB Directory structure: gitextract_oyj908wi/ ├── .github/ │ └── workflows/ │ └── continuous_integration._yml_ ├── .gitignore ├── CHANGELOG.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── Makefile ├── README.md ├── bin/ │ └── console ├── composer.json ├── config/ │ ├── bundles.php │ ├── packages/ │ │ ├── cache.yaml │ │ ├── framework.yaml │ │ └── routing.yaml │ ├── preload.php │ ├── routes/ │ │ └── framework.yaml │ ├── routes.yaml │ └── services.yaml ├── public/ │ └── index.php └── src/ ├── Controller/ │ └── .gitignore └── Kernel.php ================================================ FILE CONTENTS ================================================ ================================================ FILE: .github/workflows/continuous_integration._yml_ ================================================ name: Continuous integration on: [push] jobs: ci: name: Continuous Integration runs-on: ${{ matrix.operating-system }} strategy: fail-fast: false matrix: operating-system: [ubuntu-latest] php-versions: ['8.1'] node-version: ['16.17'] services: mysql: image: mysql:8.0 env: MYSQL_ROOT_PASSWORD: 'Password123!' ports: - 3306:3306 steps: - name: Checkout uses: actions/checkout@v2 - name: Setup PHP, with composer and extensions uses: shivammathur/setup-php@v2 with: php-version: ${{ matrix.php-versions }} extensions: mbstring, xml, ctype, iconv, intl - name: Setup Node uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - name: Get composer cache directory id: composer-cache run: echo "::set-output name=dir::$(composer config cache-files-dir)" - name: Cache composer dependencies uses: actions/cache@v1 with: path: ${{ steps.composer-cache.outputs.dir }} key: ${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }} restore-keys: ${{ runner.os }}-composer- - name: Install run: make install-env env=test db_user=root db_password=Password123! db_host=127.0.0.1 db_name=iletaitunefoisundev - name: Analyze run: make analyse - name: Tests run: make tests-wc ================================================ FILE: .gitignore ================================================ ###> symfony/framework-bundle ### /.env.local /.env.local.php /.env.*.local /config/secrets/prod/prod.decrypt.private.php /public/bundles/ /var/ /vendor/ ###< symfony/framework-bundle ### ================================================ FILE: CHANGELOG.md ================================================ # CHANGELOG Le `changelog` liste toutes les nouveautés intégrées à chaque `release`. Ce projet respecte [Semantic Versioning](https://semver.org/) et les [recommandations](https://keepachangelog.com/en/1.0.0/). ## [2022-09-04] 0.1.0 * Installation du domaine métier [#274](https://github.com/incentive-factory/iletaitunefoisundev/issues/274) * Inscription [#283](https://github.com/incentive-factory/iletaitunefoisundev/issues/283) * Modifier le profil d'un joueur [#284](https://github.com/incentive-factory/iletaitunefoisundev/issues/284) * Validation d'une inscription [#285](https://github.com/incentive-factory/iletaitunefoisundev/issues/285) * Modifier le mot de passe [#286](https://github.com/incentive-factory/iletaitunefoisundev/issues/286) * Lister les formations [#289](https://github.com/incentive-factory/iletaitunefoisundev/issues/289) * Afficher une formation [#290](https://github.com/incentive-factory/iletaitunefoisundev/issues/290) * Commencer une formation [#291](https://github.com/incentive-factory/iletaitunefoisundev/issues/291) * Connexion [#298](https://github.com/incentive-factory/iletaitunefoisundev/issues/298) * Vérifier si l'utilisateur à valider son inscription [#310](https://github.com/incentive-factory/iletaitunefoisundev/issues/310) * Gérer l'erreur dans le cas ou le fetch renvoie null [#319](https://github.com/incentive-factory/iletaitunefoisundev/issues/319) * Afficher les cours d'une formation [#322](https://github.com/incentive-factory/iletaitunefoisundev/issues/322) * Lister les parcours d'un joueur [#295](https://github.com/incentive-factory/iletaitunefoisundev/issues/295) * Afficher un parcours [#318](https://github.com/incentive-factory/iletaitunefoisundev/issues/318) * Afficher un cours [#292](https://github.com/incentive-factory/iletaitunefoisundev/issues/292) * Commencer un cours [#293](https://github.com/incentive-factory/iletaitunefoisundev/issues/293) * Afficher un l'avancement d'un cours [#327](https://github.com/incentive-factory/iletaitunefoisundev/issues/327) * Terminer un cours [294](https://github.com/incentive-factory/iletaitunefoisundev/issues/294) ================================================ FILE: CODE_OF_CONDUCT.md ================================================ # Contributor Covenant Code of Conduct ## Our Pledge We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. ## Our Standards Examples of behavior that contributes to a positive environment for our community include: * Demonstrating empathy and kindness toward other people * Being respectful of differing opinions, viewpoints, and experiences * Giving and gracefully accepting constructive feedback * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience * Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: * The use of sexualized language or imagery, and sexual attention or advances of any kind * Trolling, insulting or derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or email address, without their explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Enforcement Responsibilities Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. ## Scope This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at **thomas@iletaitunefoisun.dev**. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. ## Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: ### 1. Correction **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. ### 2. Warning **Community Impact**: A violation through a single incident or series of actions. **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. ### 3. Temporary Ban **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. ### 4. Permanent Ban **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. **Consequence**: A permanent ban from any sort of public interaction within the community. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations]. [homepage]: https://www.contributor-covenant.org [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html [Mozilla CoC]: https://github.com/mozilla/diversity [FAQ]: https://www.contributor-covenant.org/faq [translations]: https://www.contributor-covenant.org/translations ================================================ FILE: CONTRIBUTING.md ================================================ # Contribution Veuillez prendre un moment pour prendre connaissance de ce document afin de suivre facilement le processus de contribution. ## Issues [Issues](https://github.com/incentive-factory/iletaitunefoisundev/issues) est le canal idéal pour les rapports de bug, les nouvelles fonctionnalités ou pour soumettre une `pull requests`, cependant veillez à bien respecter les restrictions suivantes : * N'utiliser par ce canal pour vos demandes d'aide personnelles (utilisez [Stack Overflow](http://stackoverflow.com/)). * Il est interdit d'insulter ou d'offenser d'une quelconque manière en commentaire d'un `issue`. Respectez les opinions des autres et rester concentré sur la discussion principale. * Quand vous rédigez une issue, sélectionnez le label `En attente`. Un maintainer s'occupera de valider l'issue afin de commencer à la traiter. * Chaque issue est symbolisée par les labels suivants : * Priorité * Complexité * Types ## Rapport de bug Un bug est une erreur concrète, causée par le code présent dans ce `repository`. Guide : 1. Assurez-vous de ne pas créer un rapport déjà existant, pensez à faire une recherche avant de publier une issue. 2. Vérifiez que le bug est corrigé, en essayant sur la dernière version du code sur la branche `production` ou `develop`. 3. Isolez le problème permet de créer un scénario de test simple et identifiable. ## Nouvelle fonctionnalité Il est toujours apprécié de proposer de nouvelles fonctionnalités. Cependant, prenez le temps de réfléchir, assurez-vous que cette fonctionnalité correspond bien aux objectifs du projet. C'est à vous de présenter des arguments solides pour convaincre les développeurs du projet des bienfaits de cette fonctionnalité. ## Pull request De bonnes `pull requests` sont d'une grande aide. Elles doivent rester dans le cadre du projet et ne doit pas contenir de `commits` non lié au projet. Veuillez demander avant de poster votre `pull request`, autrement vous risquez de passer gaspiller du temps de travail, car l'équipe projet ne souhaite pas intégrer votre travail. Suivez ce processus afin de proposer une `pull request` qui respecte les bonnes pratiques : 1. Forkez le repository sur votre compte 2. Créez une nouvelle branche qui contiendra votre fonctionnalité, modification ou correction : * Pour une nouvelle fonctionnalité ou modification : ``` git checkout develop git checkout -b feature/ ``` * Pour une nouvelle correction : ``` git checkout production git checkout -b hotfix/ ``` *Vous pouvez aussi utiliser [git-flow](https://danielkummer.github.io/git-flow-cheatsheet/index.fr_FR.html) pour simplifier la gestion de vos branches :* * Pour une nouvelle fonctionnalité ou modification : ``` git flow feature start ``` * Pour une nouvelle correction : ``` git flow hotfix start ``` 3. `Commit` vos changements, veillez à respecter la convention de nommage de vos `commits` de la manière suivante : ``` :