Issue Assignment Guidelines and Collaboration Process 📌
📝 Issue Assignment: Before you start working on any issues, please make sure that the issue is assigned to you. If it's a new issue, create one if it doesn't already exist. 📌
👤 One person will be assigned one issue at a time. When you raise a pull request for that issue, only then can you create the next issue. Work on one issue at a time, and once the pull request for that issue gets merged, you can create another issue. This approach allows maximum contributors to have a chance to contribute, resulting in more work being done on the repository. 🏃♂
🚫 Avoid Direct PRs: Refrain from creating direct pull requests (PRs) for issues that are already assigned to someone else. This helps prevent duplicated efforts and keeps our work organized. Even if an issue is not assigned to anyone, you should create the issue first. Only when a maintainer assigns it to you, you can then raise a PR. 🚧
Please follow these guidelines and avoid making direct PR.
Issue Assignment Guidelines and Collaboration Process 📌 📝 Issue Assignment: Before you start working on any issues, please make sure that the issue is assigned to you. If it's a new issue, create one if it doesn't already exist. 📌
👤 One person will be assigned one issue at a time. When you raise a pull request for that issue, only then can you create the next issue. Work on one issue at a time, and once the pull request for that issue gets merged, you can create another issue. This approach allows maximum contributors to have a chance to contribute, resulting in more work being done on the repository. 🏃♂
🚫 Avoid Direct PRs: Refrain from creating direct pull requests (PRs) for issues that are already assigned to someone else. This helps prevent duplicated efforts and keeps our work organized. Even if an issue is not assigned to anyone, you should create the issue first. Only when a maintainer assigns it to you, you can then raise a PR. 🚧
Please follow these guidelines and avoid making direct PR.