You can create a github PR template in the repository that has instructions on what you expect for the PRs. This would hopefully include things like: is there a jira? does the title have the jira in it? have your run `foo` command to test and verify there are no errors etc:
https://github.com/apache/metron/blob/master/.github/PULL_REQUEST_TEMPLATE.md On January 25, 2019 at 09:22:22, James Ring (s...@jdns.org) wrote: On Fri, Jan 25, 2019 at 6:17 AM Stefan Bodewig <bode...@apache.org> wrote: > > On 2019-01-25, Gilles Sadowski wrote: > > > By chance, I opened and read an automated mail from "GitBox" whose > > subject line did not contain anything that would usually prompt a > > reaction from me.[1] > > [Sidenote: I also find it annoying that the messages no longer contain > the name of the repository since we've switched to gitbox] > > > Could someone with a GitHub account please engage with the "unknown" > > people and let them know how to contribute ("dev" ML subscription, > > JIRA reports, etc.)? > > There is a CONTRIBUTING.md file in your repository that explicitly tells > people to prefer JIRA but also explicitly talks about github pull > requests. This is the boilerplate file created from the commons parent > build but you can certainly change it to fit MATH's prefered way of > operating. > > That being said, nobody is going to guarantee people will bother reading > the document. Also some contributors simply prefer using the github > interface and will rather not provide a patch at all than using diff and > JIRA. I've seen github projects that use non-github issue trackers, those projects sometimes create an issue template indicating the correct place to create issues (see https://help.github.com/articles/manually-creating-a-single-issue-template-for-your-repository/). Just a thought. > You (as in "the MATH community") need to decide whether you'd like to > forgo such contributions. It may very well be there are people who like > to use the github UI (Gary seems to be one of them :-) > > > How can we make more prominent that GitHub is not our primary way to > > interact about Apache projects. Or is it? Did I miss a change of > > policy? > > It has been added as an option but each community is certainly free to > use or do without that option. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
