๐Ÿ“ฆ Thomas-Shephard / collaborative-software-development

โ˜… 3 stars โ‘‚ 0 forks ๐Ÿ‘ 3 watching
๐Ÿ“ฅ Clone https://github.com/Thomas-Shephard/collaborative-software-development.git
HTTPS git clone https://github.com/Thomas-Shephard/collaborative-software-development.git
SSH git clone git@github.com:Thomas-Shephard/collaborative-software-development.git
CLI gh repo clone Thomas-Shephard/collaborative-software-development
Peter Foster Peter Foster feat: student statistics api integration (#205) fad4dd8 1 months ago ๐Ÿ“ History
๐Ÿ“‚ main View all commits โ†’
๐Ÿ“ .github
๐Ÿ“ src
๐Ÿ“ tests
๐Ÿ“„ .dockerignore
๐Ÿ“„ .editorconfig
๐Ÿ“„ .env.example
๐Ÿ“„ .gitignore
๐Ÿ“„ backend.slnx
๐Ÿ“„ docker-compose.yml
๐Ÿ“„ gemini.md
๐Ÿ“„ README.md
๐Ÿ“„ README.md

Collaborative Software Development

API Testing with Scalar

This project automatically compiles a list of its endpoints through scalar for testing purposes. You may access this locally at http://localhost/scalar or when deployed at https://jahoot.net/scalar.

GitHub Pull Request Titles

This project adheres to the Conventional Commits specification for GitHub Pull Request titles. This standard provides a set of rules for creating an explicit and readable history in the main branch.

The GitHub Pull Request title should be structured as follows:

<type>: <description>

Type

The type must be one of the following:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to our CI configuration files and scripts
  • revert: Reverts a previous commit

Description

A short, imperative tense description of the change in lowercase.

The description should complete the sentence "This Pull Request will ".

Example:

feat: implement user login functionality