Visual flow is a convenient ELT tool made by developers for developers. We’re not only focused on reducing your time and business expenses from a strategic perspective, we also care about the convenience of day-to-day work. That’s why we’re so inspired to co-create with you!
First off, thanks for taking the time to contribute!
Did you find a bug?
Make sure the bug has not already been reported by searching on GitHub under Issues.
If you’re unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring. For more detailed information on submitting a bug report and creating an issue, visit our reporting guidelines.
Did you write a patch that fixes a bug?
Open a new GitHub pull request with the patch. The development team will be reviewing pull requests on a regular basis and according to the team’s priorities and bandwidth.
Make sure the PR description clearly describes the problem and solution. Include the relevant issue number, if applicable.
Did you fix whitespace, format code, or make a purely cosmetic patch?
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of Visual Flow will not be accepted.
Do you intend to add a new feature or change an existing one?