Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] 103 Contributions pending on GitHub

If you add a CONTRIBUTING file to the root of your repo, GitHub will add a link when a contributor tries to create a PR [1].

Perhaps a good easy step for projects who don't want to use GitHub could add this file that clearly states that GitHub PRs will be ignored and instructions of where to send the patch to instead.


Thanh

[1] https://github.com/blog/1184-contributing-guidelines


On 18/12/13 05:01 AM, Aleksandar Kurtakov wrote:
As a Linux Tools representative I can easily say that none of the active contributors ever looked at this repo which has all the attributes to look like oficially blessed by eclipse.org. I would say that most are not aware of such a repo at all so pull requests either has to be disabled or give the possibility for projects to opt-out and request such a repo not be created at all.

Alexander Kurtakov
Red Hat Eclipse team

----- Original Message -----
From: "Mickael Istria" <mistria@xxxxxxxxxx>
To: "Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
Sent: Wednesday, December 18, 2013 11:36:06 AM
Subject: [cross-project-issues-dev] 103 Contributions pending on GitHub

I've re-run the same script, and it appears that 103 contributions are
pending for Eclipse projects on GitHub:

acceleo: 0 issues, 3 open pull requests
aether-ant: 0 issues, 1 open pull requests
bpmn2-modeler: 0 issues, 2 open pull requests
clatest: 3 issues, 3 open pull requests
e4.tools: 0 issues, 1 open pull requests
ecf: 0 issues, 1 open pull requests
eclipse.jdt.core: 0 issues, 1 open pull requests
eclipse.jdt.debug: 0 issues, 2 open pull requests
eclipse.jdt.ui: 2 issues, 2 open pull requests
eclipse.platform.common: 0 issues, 1 open pull requests
eclipse.platform.ua: 0 issues, 2 open pull requests
eclipse.platform.ui: 0 issues, 2 open pull requests
egit: 0 issues, 1 open pull requests
egit-github: 0 issues, 7 open pull requests
emf: 0 issues, 1 open pull requests
emf.texo: 0 issues, 1 open pull requests
gemini.blueprint: 0 issues, 1 open pull requests
gemini.jpa: 0 issues, 2 open pull requests
jetty.project: 0 issues, 3 open pull requests
jgit: 0 issues, 8 open pull requests
linuxtools: 0 issues, 3 open pull requests
lyo.testsuite: 0 issues, 1 open pull requests
m2e-core: 0 issues, 4 open pull requests
m2e-discovery-catalog: 0 issues, 1 open pull requests
m2e.wtp: 0 issues, 1 open pull requests
nebula: 0 issues, 1 open pull requests
nebula.widgets.nattable: 0 issues, 3 open pull requests
org.aspectj: 0 issues, 1 open pull requests
orion.client: 0 issues, 8 open pull requests
planeteclipse.org: 0 issues, 1 open pull requests
rap: 0 issues, 1 open pull requests
rap.incubator.fileupload: 0 issues, 1 open pull requests
rap.incubator.gef: 0 issues, 1 open pull requests
recommenders: 0 issues, 1 open pull requests
rmf: 0 issues, 1 open pull requests
rt.equinox.bundles: 0 issues, 1 open pull requests
rt.equinox.p2: 0 issues, 4 open pull requests
tycho: 0 issues, 4 open pull requests
vert.x: 0 issues, 13 open pull requests
webtools.jsdt.core: 0 issues, 3 open pull requests
webtools.jsdt.tests: 0 issues, 2 open pull requests
webtools.sourceediting: 0 issues, 1 open pull requests
webtools.webservices: 0 issues, 1 open pull requests
========================================
TOTAL: 5 issues, 103 open pull requests


Wouldn't it be better to disable pull requests for Eclipse repository mirrors
at GitHub? Or enforce usage of a hook on pull request telling to use
Bugzilla & Gerrit?

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top