git clone https://github.com/kwlockwo/dfl-manager.git
cd dfl-manager/code

Important: Run this setup script to install automated testing hooks:

.githooks/setup.sh

This will configure git to run tests automatically before each commit, ensuring code quality.

1. Make sure you're on the latest main branch:

   git checkout main
   git pull origin main

2. Create a feature branch:

   git checkout -b feature/your-feature-name

1. Make your code changes

2. Run tests manually to verify:

   mvn test

3. Commit your changes:

   git add .
   git commit -m "Your commit message"

   Note: The pre-commit hook will automatically run tests. If they fail, your commit will be blocked.

The pre-commit hook automatically runs BaseHandlerTest before each commit:

• ✅ If tests pass → commit proceeds
• ❌ If tests fail → commit is blocked

To skip the hook (not recommended):

git commit --no-verify -m "Your message"

mvn test

mvn test -Dtest=BaseHandlerTest

mvn test -q

• All handlers must extend BaseHandler
• Use ServiceFactory for service instantiation
• Call ensureLoggingConfigured() at the start of execute() methods

• Create services via ServiceFactory.getInstance().createXxxService()
• Never use new XxxServiceImpl() directly

• Use TransactionHelper.executeInTransaction() for database operations
• This provides automatic rollback on exceptions

1. Push your feature branch:

   git push origin feature/your-feature-name

2. Create a pull request on GitHub

3. Ensure all tests pass in CI

4. Request review from maintainers

5. Address any feedback

6. Once approved, it will be merged to main

mvn clean compile

mvn clean package

If the pre-commit hook isn't running:

1. Check if hooks are configured:

   git config core.hooksPath

   Should output: .githooks

2. Re-run the setup script:

   .githooks/setup.sh

3. Verify hook is executable:

   ls -la .githooks/pre-commit

1. Make sure you're on the latest main:

   git checkout main
   git pull

2. Clean and rebuild:

   mvn clean compile

3. Run tests:

   mvn test

• Check the TEST_SUMMARY.md for testing documentation
• Review .githooks/README.md for git hooks documentation
• Open an issue on GitHub for help

[Add your license information here]