Files
pezkuwi-sdk/docs/contributor/PULL_REQUEST_TEMPLATE.md
T
pezkuwichain 90fd044766 fix: Complete snowbridge pezpallet rebrand and critical bug fixes
- snowbridge-pezpallet-* → pezsnowbridge-pezpallet-* (201 refs)
- pallet/ directories → pezpallet/ (4 locations)
- Fixed pezpallet.rs self-include recursion bug
- Fixed sc-chain-spec hardcoded crate name in derive macro
- Reverted .pezpallet_by_name() to .pallet_by_name() (subxt API)
- Added BizinikiwiConfig type alias for zombienet tests
- Deleted obsolete session state files

Verified: pezsnowbridge-pezpallet-*, pezpallet-staking,
pezpallet-staking-async, pezframe-benchmarking-cli all pass cargo check
2025-12-16 09:57:23 +03:00

75 lines
2.1 KiB
Markdown

## Description
<!-- A concise description of what your PR does and what issue it solves -->
<!-- Use GitHub semantic linking: Fixes #123, Closes #456 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] Pezpallet change (changes to custom pallets in `/pezkuwi/pallets/`)
- [ ] Runtime change (changes to runtime configuration)
- [ ] XCM/Cross-chain change
- [ ] Documentation update
- [ ] CI/CD change
## Changes Made
<!-- List the specific changes made in this PR -->
-
## Testing
<!-- Describe the tests you ran and how to reproduce them -->
- [ ] Unit tests pass (`cargo test`)
- [ ] Build succeeds (`cargo build --release`)
- [ ] Benchmarks compile (`cargo build --release --features runtime-benchmarks`)
- [ ] Manual testing completed (describe below)
### Test Details
<!-- How did you test this change? -->
## Checklist
- [ ] My code follows the project's style guidelines
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged and published
## Security Considerations
<!-- For changes to pallets, runtime, or financial logic -->
- [ ] No new security vulnerabilities introduced
- [ ] Financial calculations reviewed for overflow/underflow
- [ ] Access control properly implemented
- [ ] No sensitive data exposed
## Breaking Changes
<!-- If this is a breaking change, describe the impact and migration path -->
N/A
## Related Issues/PRs
<!-- Link any related issues or PRs -->
-
---
**For Reviewers:**
- Check that tests cover the changes adequately
- Verify no regressions in existing functionality
- For pezpallet changes: review weight calculations
- For XCM changes: verify cross-chain compatibility