Add Gerber Builder Bug template

.github/ISSUE_TEMPLATE/builder_gerber.md

@@ -0,0 +1,89 @@
+---
+name: Gerber Builder Bug Report
+about: Report a bug in Gerber Code Builder (`pygerber.builder.gerber`).
+title: "[Gerber Builder]: <when-i-am-doing-something-then-something-fails>"
+labels: ["gerber-builder", "bug", "waiting-for-checkboxes"]
+projects: ["argmaster/3"]
+assignees: "Argmaster"
+---
+
+# Gerber Builder Bug Report
+
+## Mandatory checks
+
+> Checks listed below are mandatory for opening a new issue.
+
+> If haven't done any of the checks listed below, please do that, we will not look into
+> the issue until all of the checks in mandatory checks section are checked.
+
+### Before opening this issue:
+
+- [ ] I have reviewed the README for guidelines and haven't found a solution there.
+- [ ] I have reviewed the PyGerber documentation and haven't found a solution there.
+- [ ] I have reviewed the existing open issues and verified that this is not a
+      duplicate.
+- [ ] I have reviewed the existing closed issues and verified that this was already
+      resolved or marked as won't fix.
+- [ ] I have reviewed the existing pull requests and verified that this is not a already
+      known issue.
+- [ ] I have reviewed the existing discussions and verified that this is not a already
+      known issue.
+
+> If you have found a issue / discussion / pull request describing similar but not quite
+> matching issue, You can still open new issue, we will review it and decide if we want
+> to merge them. If you can, please reference this issue here:
+
+## To Reproduce
+
+> Please provide minimal Python script reproducing the issue. If the issue is related to
+> code generated by the builder, please provide example generated code. If the code is
+> confidential, follow guidelines regarding confidential files available in
+> `Additional context` section below.
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+## Expected behavior
+
+> A clear and concise description of what you expected to happen, what code should be
+> generated or how builder should behave.
+
+## Additional context
+
+> If applicable, add screenshots, code examples, or any other resources that can speed
+> up process of reproducing and fixing the issue.
+
+> If your issue was discovered with use of specific source file (e.g. in Gerber format),
+> please attach it to the issue. If file is confidential, please create minimal subset
+> of the file which can be shared in public and allows to reproduce the issue.
+
+> If you are not able to create minimal reproduction for confidential source, you can
+> email me the confidential file at `[email protected]` with the issue title in
+> the subject. I will not share the file anywhere in public and will delete it after the
+> issue is resolved. We can discuss NDA agreements via email if needed.
+
+> You still should create a public issue based on this template for the issue to be
+> investigated, please use `<confidential-file>`, `<confidential-image>`, etc. as a
+> placeholders for the confidential files.
+
+## Environment:
+
+**Please complete the following information:**
+
+- Operating system: [e.g. `Ubuntu 24.04`]
+- Python version: [e.g. `3.9.0`]
+- PyGerber version: [e.g. `3.0.0`]
+
+## Optional checks
+
+> Agreements listed below are optional, but consider checking them if it is not harmful
+> for you to do so. You can greatly improve PyGerber doing by checking them.
+
+- [ ] I want to contribute example source files attached to this issue in the test suite
+      of PyGerber for regression testing purposes.
+- [ ] I want to include separate LICENSE file for resource files attached as a result of
+      an agreement described in first checkbox in this section.
+- [ ] I want to include separate README file for resource files attached as a result of
+      an agreement described in first checkbox in this section.