You can customize the information displayed in
pull requests(jflory7,
13:46:49)
Includes what branch and repo pull requests go
into, add a note about contributing (e.g. "how to test your changes
before submitting")(jflory7,
13:47:22)
Q: "Can we compare against dates? e.g. Jan 1
and Mar 30?"(jflory7,
13:50:36)
A: Currently not, only two commits. Technically
possible, no reason why not. Merge commits could affect whether this
is accurate or not as well, e.g. if changes were made before date,
but were merged in during that timeframe(jflory7,
13:52:07)
=== Take issue (Ryan Lerch) ===(jflory7,
13:52:43)
Before, if you wanted to take an issue, you
needed to edit metadata, find your username, save metadata(jflory7,
13:53:11)
Now, you click the button in the issue and you
will auto-assign it to yourself. No refresh necessary(jflory7,
13:53:28)
Q: "Right now, if you have page open for a long
time, will it work?"(jflory7,
13:53:47)
A: Will work because connection never closes.
Problem is that some endpoints is over cross-site scripting, other
concerns as well were considered too.(jflory7,
13:54:50)
=== Live completion (Eric Barbour) ===(jflory7,
13:55:01)
Auto-completion for tagging username or IDs for
tickets / PRs, e.g. @jflory7 or #17(jflory7,
13:55:27)
=== README file at creation (Ryan Lerch)
===(jflory7,
13:56:08)
Most people used to git, not a problem, but
more in mind for new users(jflory7,
13:56:18)
Want to have Pagure as front-end for
dist-git(jflory7,
13:57:19)
Run x instances of Pagure for x instances of
pkgdb, not effective solution when you can just run one. Won't be
able to search between Pagures.(jflory7,
13:58:16)
Adding namespacing would break all previous
projects and change all URLs for all projects(jflory7,
13:58:43)
Solution? Adding one slash to the end of a
project configuration(jflory7,
13:59:48)
ReadTheDoc hook: Push to PAgure, update
ReadTheDocs(jflory7,
14:03:14)
Block un-signed commits: Blocks PRs from being
merged if they are unsigned with GPG(jflory7,
14:03:37)
Block non-fastforward commits: If you want to
keep the log clean, keeps merge commits out and only relevant
commits (can also specify which branch to have this apply to, e.g.
`master`)(jflory7,
14:04:26)
Designed to be made so you can move things from
Pagure instance to Pagure instance(jflory7,
14:11:52)
Maybe you have a private Pagure instance and
want everyone to be on there, should be able to port all packages
over to the other instance(jflory7,
14:12:26)
When you push to Pagure, it will do a git push
to another git server(jflory7,
14:12:43)
56 contributors, 33 contributors at 1.0, 2 GSoC
students this year (Vivek Anand & Farhaan Bukhsh), 2 Red Hat
interns (Eric Barbour and Simon)(jflory7,
14:13:51)