Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
194 changes: 97 additions & 97 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,98 +1,98 @@
SUMMARY
-------
Describe what this Pull Request changes and why.
TYPE OF CHANGE
--------------
Select all that apply:
[ ] fix: Bug fix (non-breaking change)
[ ] feat: New feature (non-breaking change)
[ ] refactor: Code change that neither fixes a bug nor adds a feature
[ ] docs: Documentation-only changes
[ ] test: Tests only
[ ] chore: Maintenance / tooling changes
[ ] perf: Performance improvement
[ ] build/ci: Build or CI changes
RELATED ISSUES
--------------
Link related issues (if any):
- Closes #
- Relates to #
HOW TO TEST
-----------
Provide clear steps to validate this change:
1.
2.
3.
If no tests were run, explain why.
BEHAVIOR CHANGES
----------------
Explain any user-visible or operational behavior changes
(CLI output, process lifecycle, config semantics, logs, permissions, etc.).
SECURITY AND ISOLATION
---------------------
Does this Pull Request affect any of the following?
[ ] Privilege boundaries / user isolation
[ ] Filesystem permissions / ownership
[ ] Process execution (os/exec, syscalls)
[ ] Network exposure / listeners
[ ] Logging of sensitive data
If any are checked, explain the risk and mitigations.
CONFIGURATION CHANGES
---------------------
[ ] No configuration changes
[ ] Configuration changes included (describe below)
If configuration changes are included, provide examples (redact secrets).
(paste config here)
DOCUMENTATION
-------------
[ ] No documentation needed
[ ] Documentation updated (README / docs / comments)
LICENSE ALIGNMENT (Apache 2.0)
------------------------------
Confirm that this Pull Request:
[ ] Does not introduce proprietary or closed-source dependencies
[ ] Contributions are submitted under the Apache License, Version 2.0
CHECKLIST
---------
[ ] I followed the repository conventions (Conventional Commits, branch naming)
[ ] I kept the change scoped and reviewable
[ ] I added or updated tests when appropriate
[ ] I ran go test ./... (or explained why not)
SUMMARY
-------

Describe what this Pull Request changes and why.


TYPE OF CHANGE
--------------

Select all that apply:

[ ] fix: Bug fix (non-breaking change)
[ ] feat: New feature (non-breaking change)
[ ] refactor: Code change that neither fixes a bug nor adds a feature
[ ] docs: Documentation-only changes
[ ] test: Tests only
[ ] chore: Maintenance / tooling changes
[ ] perf: Performance improvement
[ ] build/ci: Build or CI changes


RELATED ISSUES
--------------

Link related issues (if any):

- Closes #
- Relates to #


HOW TO TEST
-----------

Provide clear steps to validate this change:

1.
2.
3.

If no tests were run, explain why.


BEHAVIOR CHANGES
----------------

Explain any user-visible or operational behavior changes
(CLI output, process lifecycle, config semantics, logs, permissions, etc.).


SECURITY AND ISOLATION
---------------------

Does this Pull Request affect any of the following?

[ ] Privilege boundaries / user isolation
[ ] Filesystem permissions / ownership
[ ] Process execution (os/exec, syscalls)
[ ] Network exposure / listeners
[ ] Logging of sensitive data

If any are checked, explain the risk and mitigations.


CONFIGURATION CHANGES
---------------------

[ ] No configuration changes
[ ] Configuration changes included (describe below)

If configuration changes are included, provide examples (redact secrets).

(paste config here)


DOCUMENTATION
-------------

[ ] No documentation needed
[ ] Documentation updated (README / docs / comments)


LICENSE ALIGNMENT (MIT)
-----------------------

Confirm that this Pull Request:

[ ] Does not introduce proprietary or closed-source dependencies
[ ] Contributions are submitted under the MIT License


CHECKLIST
---------

[ ] I followed the repository conventions (Conventional Commits, branch naming)
[ ] I kept the change scoped and reviewable
[ ] I added or updated tests when appropriate
[ ] I ran go test ./... (or explained why not)
[ ] I ran golangci-lint run (or explained why not)
Loading