Finish repo configuration

Question

alilloig opened this issue 2 years ago · 0 comments

Repository template

A template enabled repository, including all necesary files to open source

(create an issue with the following content if you want to track the repo configuration)

Repository info
- Add repo description
- Update website to https://onflow.org
- Add relevant repository topics (i.e. blockchain onflow, etc)
Define merge workflow
- main branch rule:
  - Require pull request reviews before merging (1 approving review)
    - Require review from Code Owners
  - Require status checks to pass before merging
    - Require branches to be up to date before merging
  - Require linear history
  - Restrict who can push to matching branches
    - Choose onflow/flow team
Add necessary team members, adjust access levels
- onflow/flow-admin ⇒ Admin access
- onflow/flow ⇒ Write access
Add issue tags
- Architecture
- Backend
- Breaking Change
- Dev Portal Documentation
- Feature
- Feedback
- Frontend
- improvement
- integration testing
- Metadata View
- MoSCoW - Must
- MoSCoW - Should
- MoSCoW - Could
- MoSCoW - Would
- Needs Definition
- Needs Estimation
- Needs Test Cases
- P-High
- P-Low
- P-Medium
- question
- S-Access
- S-Client
- S-Collection
- S-Common
- S-Consensus
- S-Cryptography
- S-Emulator
- S-Execution
- S-FCL
- S-Go SDK
- S-Infrastructure
- S-JS-SDK
- S-Language
- S-Network Layer
- S-Playground
- S-PostExecution
- S-Semantics
- S-Verification
- T-Bug
- T-Documentation 📃
- T-Meta
- Technical Debt