🎉🥳 Thank you for contributing! 🥳🎉
We truly appreciate your help in making Apex Log MCP Server better. Whether you're fixing a bug, adding a feature, or improving documentation, your contributions are invaluable to us!
Before you dive in, please make sure to review our code of conduct to ensure a welcoming environment for everyone.
- Check out the open issues first to see if your idea or bug has already been reported.
- If you don’t see anything related, open an issue! We’d love to hear your thoughts and provide feedback or suggestions before you get started. This helps avoid duplicate work and ensures we’re aligned.
For detailed instructions on setting up your development environment, refer to the Development Guide.
We can't wait to see your contributions! Whether it’s fixing a bug, adding a new feature, or improving the docs, we truly appreciate your time and effort.
- Fork the repo.
- Clone your fork locally.
- Create a feature branch e.g (
feat-some-descriptionorbug-some-description). - Make your changes.
- Push your changes.
- Open a PR for review!
- We follow a simple format for commit messages: Conventional Commits
- Use the imperative mood in the subject line (e.g., "fix: date parsing in log parser" rather than "fixed date parsing in log parser").
feat: add namespace filtering to performance analysisfix: handle empty debug logs gracefullydocs: add Claude Desktop configuration examplerefactor: simplify trace flag validationtest: add coverage for bottleneck detection
Please verify the following before opening a PR:
- All tests pass (
pnpm test) - TypeScript compiles without errors (
pnpm run build) - Linting passes (
pnpm run lint) - New features include tests where appropriate
If you get stuck at any point, feel free to open an issue or reach out to us in the discussions tab. We’re here to help and we want to make your contribution experience as smooth as possible. 🤗
Thank you again for contributing to Apex Log MCP Server! Your input helps make this tool even better for Salesforce developers. 🙌