Contributing

We welcome contributions of all kinds: bug fixes, new features, documentation improvements, and test coverage. Here's how to get involved.

1. Fork the repository on GitHub
2. Clone your fork locally:

   git clone git@github.com:your-username/laravel-scout-bulk-actions.git
   cd laravel-scout-bulk-actions
   

3. Install dependencies:

   composer install
   

Create a branch for your work:

git checkout -b your-feature-name

Keep each pull request focused on a single change. If you're fixing a bug and improving something else, send two separate PRs. This makes review faster and keeps the git history clean.

Before submitting, run the test suite:

composer test

This runs all checks including code style, static analysis, and tests. The CI pipeline runs the same command on every pull request, so catching issues locally saves time.

1. Push your branch to your fork
2. Open a pull request against the main branch
3. Fill in the PR template with a clear description of what changed and why
4. Link any related issues

We follow Semantic Versioning. If your change is a breaking change, mention it clearly in the PR description.

Write meaningful commit messages. Each commit should represent a single logical change. If you need to clean up your history, rebase before submitting.

If you'd like to discuss a feature before writing code, start a conversation in GitHub Discussions. That's the best place to propose ideas, get feedback, and coordinate with maintainers before opening a PR.

If you discover a security vulnerability, do not open a public issue. Email hello@mozex.dev directly.