Contributing Guidelines
Since 2021, the Lightning Flow Scanner has grown from its roots as VS Code tool to empower Salesforce Developers across six free and open-source platforms—from developer tools to native Salesforce App—delivering a unified experience for robust static analysis of Flows. Our dedicated community has shared their expertise to deepen understanding of Flow optimization. Your support can amplify our impact. Here’s how you can contribute:
- 💬 Share feedback to help us improve.
- 📢 Share our work with your network.
- 💻 Contribute code by submitting pull requests.
- 🤝 Join as a member to connect.
- Sponsor the ecosystem by making a donation.
I have a Question/Feedback
For general questions, ideas, or seeking input on topics that might (or might not) turn into issues, we recommend to use our Discussions forum. This is best for open-ended conversations, brainstorming, and gathering community input before creating a feature request.
If it’s more specific like a bug or a new feature—use GitHub Issues instead. Before creating a new issue, please take a moment to search the existing Issues to prevent duplicates. If you find something relevant, adding an upvote helps us understand demand and prioritize better. We’ve prepared a few templates to guide you through the process of issue reporting:
Core Engine - For issues or requests related to the core functionality of the scanner, use the following links to submit your request:
- Report Issue: Report a bug or issue.
- Rule Request: Submit a request for a new rule.
- Features/Other: Suggest a new feature or enhancement.
Platforms - For issues related to specific platforms, use the appropriate template:
Submitting Pull Requests
We welcome pull requests! Please first make sure there is a corresponding GitHub Issue for your contribution before submitting a PR. Reference the issue clearly in your pull request and follow the provided pull request template to help us review and merge your changes efficiently.