We have this if in a couple of places and I do not understand it. What is the idea behind this?

The list of select is larger than this one which already contains one more item than you had listed.

Could you explain a little what you had in mind with this?

If there are really a lot of commits over a long period of time in the git repo, the graph becomes un-readable.

So can/should we either:

• Make the graph clickable zoom in/out with the mouse or drag to the right to see earlier commits?
• Restrict to say the last two years of history or so?

For example: http://ambre.pingoured.fr/public/pagure_mm3_history.png

To make things keep working, I just deleted these two blocks locally.

Yeah, for this presentation (which once polished well enough, will probably always be visible) restricting it to a timeframe is probably the best way to go.

Here on the commits page, it is more a item to provide a glancable indication of project activity, rather than a serous data analysis tool (IMHO)

I will also do some more scouting for different libraries to do a similar presentation, as this one also seems to pull in the DTD for the svg it generates from the github repo, which is suboptimal.

what i was trying to do here was to not display things like the tree and commits and a few others if the repo was empty. Requests doesnt make sense either if the repo is empty.

Issues does make sense if the repo is empty.

The reason for the weird conditiional referencing pages was because not all of these pages pass the repo_obj through, so we can't check if the repo is empty on those pages to show/hide the tabs.

would an solution here be to pass through a boolean on all pages if the repo is empty or not (rather than passing through the entire repo_obj for each one?)

We actually had the request to support issues only project (I figure to replace a trac used only for tickets)