pull_request_template.md

Important

• Please read our Contributing Guidelines before opening a PR.
• Before creating your PR, please ensure you read the branching strategy. The end result after completing the merge actions should be that release/XXX <= develop, where XXX is the latest released protocol version. This ensures that we minimise merge conflicts, and that work doesn't go missing.
• As per the branching strategy, you must ensure you select the correct base branch, both for branching from, and in the PR UI above. The following process can be used to decide the base branch:
  • For README changes or code changes which can wait until the next protocol update to be released, use develop. This should be the default for code changes.
  • For github workflow changes, or code changes which need to go out as a fully-interoperable update to the node at the current protocol version, use release/XXX.
    • Such changes must be tested and reviewed more carefully to mitigate the risk of regression.
    • Once the change is merged, it is the merger's responsibility to ensure release/XXX is merged into the develop branch.

Please remove this section once you confirm you follow its guidance.

Summary

Testing

Changelog