@JonathanGregory 😆 yeah at the time that I inserted that update I wasn't sure if we'd be using the most GitHub-esque way of doing Pull Requests, which is via forks of repositories, as we're doing now. In such cases that falls to the proposer, but some groups prefer workflows that use the same repository to hold all branches. It's a cultural issue and I feel that we've established we use the multi-repository workflow in CF so that's an item that should be updated in CONTRIBUTING! I hope the rest of the instructions were helpful nonetheless :)
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/258#issuecomment-637576457 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
