The pagure docs cover installation and configuration, but offer little for the end user. Of course many features are obvious, but many more are not. For example, I just learned, via a comment on an issue, that I can close a PR by pushing a properly formed commit message. I'm not sure how I'm supposed to find out about features like that.
A few topics I'd like to see covered:
I have started on this usage doc, but I got a little out of ideas on what to add, so thanks for this list :)
https://pagure.io/pagure/pull-request/858
Btw @mikem, could you expand on what you expect from the recommended workflow?
recommended workflow
Ok I think I have tackled:
and
in https://pagure.io/pagure/pull-request/898
I am tempted to close this as fix for now, feel free to re-open if you disagree or open more tickets for missing doc :)
Sure, much better now. Though would still like to see a doc on integrating with Fedora CI (or is there one that I missed?).
a doc on integrating with Fedora CI
Well there isn't really anything doing that integration yet, it's something @farhaan is working on, so it will be on his plate to write the doc :)
Pagure itself seems to have some integration with jenkins. How is that accomplished?
Well there is pagure project on jenkins but that's just following https://fedoraproject.org/wiki/Jenkins@infra while what @farhaan is working on is to complete this set-up with actually reporting the status of the tests on jenkins for new PRs.
So very similar to lubomir's approach in https://lubomir.github.io/en/2016-03-08-poor-man-ci.html but more integrated into pagure itself.