We should review all the issues that have been created in the most relevant repositories for our organization. Here they are specified:
These are the tasks that need to be completed for each repository:
| Repository |
Review code owners file |
Clean issues and PRs |
Assign priority labels |
Improve README.md |
Review branches rights |
Review CI/CD |
| Core packages |
✅ |
✅ |
✅ |
|
✅ |
✅ |
| SDK + SDK Publish |
✅ |
✅ |
✅ |
|
✅ |
✅ |
| Types |
✅ |
✅ |
✅ |
|
✅ |
✅ |
| Toolkit |
✅ |
✅ |
✅ |
|
✅ |
✅ |
| Schemas |
✅ |
✅ |
✅ |
|
✅ |
✅ |
| See and Pin |
|
|
|
|
|
|
| Certificates Server |
|
|
|
|
|
|
| Ethical Metrics |
|
✅ |
|
|
|
|
| Smoothing Pool |
|
|
|
|
|
|
| QA |
|
✅ |
|
✅ |
|
|
| Installer |
✅ |
|
|
|
✅ |
|
| Staking Brain |
✅ |
✅ |
✅ |
✅ |
✅ |
|
The recommended configuration for branch rights is the following:
Require PR before merging with:
- 1 approval
- Require review from Code Owners
- Require approval of the most recent reviewable push
- Require conversation resolution before merging
Reactions are currently unavailable
We should review all the issues that have been created in the most relevant repositories for our organization. Here they are specified:
These are the tasks that need to be completed for each repository:
The recommended configuration for branch rights is the following:
Require PR before merging with: