README

lazbounce

A simple retro ping-pong game built using Pascal programming language

Our Team

1. Janice Claresta Lingga - 32200041
2. Andrew Virya Victorio - 32200091
3. Lorne Jovan Rustiadi - 32200034
4. Stevanus Limanto - 32200022
5. Kitbert - 32200038

How to write a good commit message?

Use this conventional commit message everytime you made changes.

Semantic Commit Messages

initial commit -> Do this at the beginning of the project.

Format: <type>(scope): <subject> <scope> is optional.

eat: add hat wobble
^--^  ^------------^
|     |
|     +-> Summary in present tense.
|
+-------> Type: chore, docs, feat, fix, refactor, style, or test.

Types of Commit

• feat: The new feature you're adding to a particular application
• fix: A bug fix
• style: Feature and updates related to styling
• refactor: Refactoring a specific section of the codebase
• test: Everything related to testing
• docs: Changes to the documentation
• chore: Regular code maintenance. You can also use emojis to represent commit types
• perf: A code that improves performance
• build: Build related to changes
• ci: Continuous integration

More Examples

chore: add Oyster build script
docs: explain hat wobble
feat: add beta sequence
fix: remove broken confirmation message
refactor: share logic between 4d3d3d3 and flarhgunnstow
style: convert tabs to spaces
test: ensure Tayne retains clothing

Tips for Creating a Great Commit

1. Specify the type of commit
2. Separate the subject from the body with a blank line
3. Your commit message should not contain any whitespace errors
4. Remove unnecessary punctuation marks
5. Do not end the subject line with a period
6. Capitalize the subject line and each paragraph
7. Use the imperative mood in the subject line
8. Use the body to explain what changes you have made and why you made them
9. Do not assume the reviewer understands what the original problem was, ensure you add it
10. Do not think your code is self-explanatory
11. Follow the commit convention defined by your team