pull_request_template.md

PR Checklist

Addresses an existing open issue: closes #<the_issue_number_here>. If not, explain why (minor changes, etc.).
You have discussed this issue with the maintainers of maxGraph, and you are assigned to the issue.
The scope of the PR is sufficiently narrow to be examined in a single session. A PR covering several issues must be split into separate PRs. Do not create a large PR, otherwise it cannot be reviewed and you will be asked to split it later or the PR will be closed.
I have added tests to prove my fix is effective or my feature works. This can be done in the form of automatic tests in packages/core/_tests_ or a new or altered Storybook story in packages/html/stories (an existing story may also demonstrate the change).
I have provided screenshot/videos to demonstrate the change. If no releavant, explain why.
I have added or edited necessary documentation, or no docs changes are needed.
The PR title follows the "Conventional Commits" guidelines.

Explain the details for making this change: What existing problem does the Pull Request solve? Why is this feature beneficial?
If the Pull Request includes breaking changes, it must explicitly follow the syntax proposed by Conventional Commits (in the PR title and with a quote at this end of this overview).
Includes keywords to reference the issue, e.g., "fixes #xxxx", "closes #xxxx", ... (where #xxxx is the issue number) and automatically closes it when the Pull Request is merged. For more details about linking issues in Pull Requests, see https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.
Also include a short description of the changes in this Pull Request to be used as merge commit when merging the PR. -->