This will help: http://sindresorhus.com/github-markdown-css/
I agree that GitHub's rendering of markdown files is much better than ours. We hope to improve it. Our first interaction engineer just started and we're looking to hire more https://about.gitlab.com/jobs/
Of course, you're very welcome to submit improvements yourself, as long as you do not submit proprietary code.
* Navigation between 'root' project and per-user forks is terrible. There's no way I can see to go from the root proj (where all the issues/MRs are) to my fork. All the necessary data is available over the API, just not present on in the UI.
* Issue labelling is kinda nasty. You default to no labels for a new project, but you can 'generate' the default set. If you want to add a new label from teh 'new issue' page, it doesn't show up as an option after adding. Make it a modal or refresh teh list or something.
* You don't seem to eb able to search by commit # in the search fields?
* 'merge this MR' button sometimes just arbitrarily fails, and refreshign the page and hitting it again will work (no commits/repo changes in teh meantime)
* No equiv. of the github 'network graph' that also shows other forks.
* It took a bunch of pissing around to disable gravatar which was giving mixed content SSL warnings even though it shouldn't.
* Live preview of teh markdown input for comments/messages would be nice, especially with some apparently odd heuristics for deciding whether to autolink something like a same-repo/file:line type.
* Having read the various docs I can find a few times now, I still have no clue how to set up gitlab-CI on a self-hosted instance.
As I say, some of this is probably just not knowing where things are, but it's not for want of looking.
* I agree it is too hard to find forks. https://gitlab.com/gitlab-org/gitlab-ce/issues/2406
* I agree we should make it easier to add new labels to an issue https://gitlab.com/gitlab-org/gitlab-ce/issues/2574
* I would normally replace the full commit sha1 in the url of another commit. But feel free to add it to the search.
* That is strange, hopefully this gets better when we get rid of satellites in 8.0
* Indeed, the graph is for one repo, the calculations are done live and are cached, but doing it for many forks could take too long.
* We load the gravatar's over https by default if you enable https in gitlab.yml https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/g..., it is strange that you had a mixed content warning.
* Issue comments should have a preview tab.
* The documentation is in https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc... but after 8.0 it will be integrated in GitLab itself so you no longer have to set it up separately.
1. Google "GitLab [obvious feature]"
2. Land on feedback.gitlab.com, on a feature request with hundreds of upvotes
3. "We're accepting pull requests"
4. Filed in 2013
5. Still open
6. Sigh loudly.
7. Check the blog for what evidently more important features they've been working on instead
8. "We're very excited to announce that we'll ship GitLab Mattermost, an open source, on-premises messaging app"
9. Sigh loudly
10. Conclude that they are probably an open source company strapped for cash and to cut them some slack
11. See HN article about closing series A
12. "Oh good, now they can finally get to their epic feature backlog"
13. "I think we're already there, what would you like to see?"
14. Sigh loudly.
Don't get me wrong, I love GL. But wow is that workflow annoying.