Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/mustapha7018/a2sv-code-review-practice---pr-reviewers
A repo to practice code review. (For PR Reviewers).
https://github.com/mustapha7018/a2sv-code-review-practice---pr-reviewers
Last synced: about 2 months ago
JSON representation
A repo to practice code review. (For PR Reviewers).
- Host: GitHub
- URL: https://github.com/mustapha7018/a2sv-code-review-practice---pr-reviewers
- Owner: Mustapha7018
- Created: 2024-04-04T12:00:22.000Z (9 months ago)
- Default Branch: main
- Last Pushed: 2024-04-05T15:56:45.000Z (9 months ago)
- Last Synced: 2024-04-15T01:23:27.471Z (9 months ago)
- Language: Dart
- Size: 10.7 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# A2SV Code Review Practice - PR Creators and Reviewers 🚀
Welcome to the A2SV Code Review Practice repository! This repository is designed to facilitate practice and enhance our skills in creating and reviewing Pull Requests (PRs).
## Contributors ✍️
- Farad
- Miya
- Felix## Reviewers 🕵️
- Mustapha
- Kudus
- Erica
- Tariq## Purpose 🎯
This repo is intended for practice. It's a safe space where contributors can make PRs, and designated reviewers can leave feedback. The goal is to simulate a real-world code review process, improve our collaborative coding skills, and maintain best practices for software development within our team.## Contribution Guidelines 📝
### For PR Creators:
- Always sync and pull the latest changes before working on your new feature or fix 🔃.
- Create a new branch for each set of related changes 🔀.
- Write clear, descriptive commit messages ✉️.
- Make sure your code is well-tested before opening a PR ✅.
- Write a concise PR description detailing the changes and any other relevant information for reviewers 📄.
- Assign your PR to the designated reviewers for feedback 🤝.### For Reviewers:
- Review PRs thoroughly and provide constructive, polite, and helpful feedback 💬.
- Highlight both strengths and areas for improvement 🔍.
- If you suggest changes, be clear about why the change is necessary and how it improves the code 💡.
- Once satisfied, approve the PR so it can be merged ✔️.## Switching Roles 🔁
Roles of PR creators and reviewers will rotate to ensure everyone gets to experience both sides of the process. Communication about role changes will be conveyed through our team's communication channels.## Questions & Support ❓
For any questions or help needed, reach out to the contributors within this repository or through our designated communication channel.Let's collaborate and grow together! 🌱