We initially found Gitcord to be a valuable addition to our open-source development process. However, after using it for some time, we've identified a couple of areas for improvement:
Unrelated CI Errors Confuse Contributors: When the Gitcord CI workflow throws errors unrelated to the specific pull request (PR), it creates confusion for both contributors submitting the PR and reviewers evaluating it. This disrupts the review process and can lead to wasted time.
Discord Server Overload: Gitcord generates a separate thread for every GitHub issue and PR in our ACM Discord server. This clutters the server and makes it difficult to find relevant information.
What happened?
We initially found Gitcord to be a valuable addition to our open-source development process. However, after using it for some time, we've identified a couple of areas for improvement: