Problem
We have seen a lot of confusion around the process for working with Melvinbot in App, and we often see PRs get created and sent for review before having a proposal approved. Engineers end up having to go back and review the proposal at PR review time, which means significant contributor time and effort could be wasted if the proposal is not correct. Or, the internal engineer may not realize no proposal was approved, and waste time reviewing a PR that goes in the wrong direction.
Solution
Clearly document the process for contributors, contributor +, and internal engineers to work with Melvin on App issues, and include it in a markdown file in the repository. Likely linked from the main contributing document.
Problem
We have seen a lot of confusion around the process for working with Melvinbot in App, and we often see PRs get created and sent for review before having a proposal approved. Engineers end up having to go back and review the proposal at PR review time, which means significant contributor time and effort could be wasted if the proposal is not correct. Or, the internal engineer may not realize no proposal was approved, and waste time reviewing a PR that goes in the wrong direction.
Solution
Clearly document the process for contributors, contributor +, and internal engineers to work with Melvin on App issues, and include it in a markdown file in the repository. Likely linked from the main contributing document.