https://forge-allura.apache.org/p/allura/tickets/You searched for labels:"help"enWed, 13 Jul 2016 20:46:53 -0000https://forge-allura.apache.org/p/allura/tickets/4545/* SVN needs a new section: importing an existing SVN repo. Have a link to /p/PROJECT/admin/TOOL/importer/ * The message boxes have cursor:pointer. Perhaps we need to change/refactor that SCSS class a bit.Dave BrondsemaThu, 20 Aug 2015 22:07:57 -0000https://forge-allura.apache.org/p/allura/tickets/4545/https://forge-allura.apache.org/p/allura/tickets/4382/For each of Git, SVN, and Hg we should have instructions for how to get started with a brand new (empty) repo, and for pushing existing code to the new repo. Provide specific commands. Show the text/commands on the repo page to developers/admins if the repo is empty (or r1 for SVN)Dave BrondsemaThu, 20 Aug 2015 22:07:54 -0000https://forge-allura.apache.org/p/allura/tickets/4382/https://forge-allura.apache.org/p/allura/tickets/3593/Here's a user suggestion: * There's no obvious user path once you've created a project. Github has a numbered checklist of things you should do right after you create a project (set up private/public keys, how to do your first commit and push branches to the remote git repository, etc). This is seems like a good idea to help new project admins along. For us it would be things like give permissions to other users, add a release to download, put some documentation in your wiki, set up your repo keys, and maybe some other ones we can think about. This should show up after the project reg is complete and maybe be available for later reference from the project admin area.Jenny SteeleWed, 13 Jul 2016 20:46:53 -0000https://forge-allura.apache.org/p/allura/tickets/3593/