All changes to the repository must be done through a pull request (PR). A branch must always be created, and commits grouped together logically. Whenever asked to create commit messages, to push code, or create a pull request (PR), use this skill so everything is done correctly.
To ensure good history, all code changes need to be grouped together logically into commits, with good messages, and a branch should always be used rather than committing directly to the default branch. Follow these guidelines to ensure we are following these practices.
Before performing any commits, ensure a branch has been created for the work. This branch must never be dotnet-workshop, but should be a branch created specifically for the changes taking place. If no branch is already created, create a new one with a good name based on the changes being made.
When committing changes:
NEVER merge to the default branch unless explicitly instructed to do so by the user
Before creating a pull request, ensure all tests pass.
When creating a pull request: