On Tuesday, November 15, 2016 12:26:26 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 15, 2016 at 12:21:13PM +0100, Pavel Raiskup wrote:
> On Tuesday, November 15, 2016 8:41:26 AM CET Pavel Raiskup wrote:
> > On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
> > > On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
> > > > +1 for visibility
> > > > Also, GitHub gives people credit on their profiles for
contributions! That
> > > > may motivate them to send pull-requests.
> > >
> > > Check the next pagure release ;-)
> >
> > Bug report:
> > I've moved one pull request from github to pagure.
> >
> > Forking the project caused 404, but apparently the project was forked
> > under 'praiskup/' namespace. So I pushed the commits into separate
branch
> > and requested pull request -> and I received 404 again.
> >
> > Seems like pagure thinks I clonned from 'copr/copr/copr' instead from
> > 'copr/copr'. Can this be hot-fixed?
>
> @pingou,
>
> bug #2:
> No email notifications are sent to my INBOX.
None at all or?
For your actions or someone else's?
Argh. Scratch #2 :) and sorry, I had full INBOX -> I hope I'll get all the
messages in queue with slight delay .. without data loss.
> bug #3:
> Updating e.g. pull-request does not refresh the page, so it seems like there was
> nothing sent.
The diff or ?
The diff isn't refreshed automatically,
No no, not about asynchronous javascript ...
you need to reload, but the
notifications about the rebase/new commits should be added automatically (modulo
the SSE server running into too many open files)
I mean -> I've commented pull request, hit the "Update Issue" button, the
text
disappeared from textarea, and no text appeared (which means no page refresh
occured).
Please redirect to a proper (pagure oriented) mailing list.
Pavel