Do not open up a GitHub issue if the bug is a security vulnerability, and instead to refer to our security policy. Any sensitive issues will be removed from the public tracker.
Ensure the bug was not already reported by searching on GitHub under Issues.
If you have a feature request make a Github Discussion (see below for more information).
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 directions for reproducing the issue or an ERDDAP™ server demonstrating the expected behavior that is not occurring.
Open a new GitHub pull request (PR) with the patch.
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
Before submitting, please read the Programmer Guide (coming soon) guide to know more about coding conventions.
Suggest your change in the ERDDAP™ GitHub discussions and start writing code. Before creating the GitHub discussion, it might be helpful to read this guidance.
Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes.
See the ERDDAP™ GitHub discussions.
See the ERDDAP™ users Google group.