RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042023-12-07T08:05:26ZRhodeCode - issues
Redmine RhodeCode CE/EE - Task #5711 (Resolved): svn: make the SSL detection work better.https://issues.rhodecode.com/issues/57112023-12-07T08:05:26ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>as per discussion here: <a href="https://community.rhodecode.com/t/svn-cant-move-a-file-http-502-bad-gateway/535/13" class="external">https://community.rhodecode.com/t/svn-cant-move-a-file-http-502-bad-gateway/535/13</a></p>
<p>check if the downgrade header can be there always to support http+https traffic</p>
RhodeCode CE/EE - Task #5400 (New): User group - subgroup supporthttps://issues.rhodecode.com/issues/54002017-11-06T22:00:25ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5391 (Resolved): Secure Email changehttps://issues.rhodecode.com/issues/53912017-09-21T17:12:54ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<ul>
<li>add email requires a password</li>
<li>email is to be selected from the list instead of entered.</li>
<li>allows easier discovery of extra email addresses</li>
</ul>
RhodeCode CE/EE - Task #5343 (Resolved): SSH key management and SSH supporthttps://issues.rhodecode.com/issues/53432017-06-22T14:59:32ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Meta issue, few key points:</p>
<ul>
<li>add ability to store, remove and validate SSH keys</li>
<li>add ability to generate NEW SSH keys for users (expose private/public somehow)</li>
<li>add event to flush users keys into a destination file stored inside .ini file</li>
</ul>
RhodeCode CE/EE - Task #5202 (Resolved): run git gc and git repack on GIT repos when we have a sc...https://issues.rhodecode.com/issues/52022017-02-08T01:01:10ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #4312 (New): Storage location changeshttps://issues.rhodecode.com/issues/43122016-11-28T02:16:25ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Allow custom location per-repository to help fragmentise the source code storage</p>
<ul>
<li>Who will be allowed to change these settings.</li>
<li>What use cases would that support</li>
</ul>
RhodeCode CE/EE - Task #4299 (New): TEMPLATE repo groupshttps://issues.rhodecode.com/issues/42992016-10-26T23:00:16ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Placeholder repo for specs about TEMPLATE repo groups that can be used for creation of pre-defined projects</p>
RhodeCode CE/EE - Task #4251 (Feedback): [customer] Pull request with subreposhttps://issues.rhodecode.com/issues/42512016-09-29T13:41:00ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>While a lot of time passed since we’ve exchanged emails last time, let me share some details about the way we work at R and what kind of Rhodecode improvements would be useful for us. </p>
<ul>
<li>Most of our iOS/Mac product repositories are Mercurial </li>
<li>We extensively use Mercurial’s subrepositories for internal dependencies: our internal libraries are Mercurial or git repositories, which are added to product repository as a subrepo. </li>
<li>I like github flow: creating feature branches (bookmarks in Mercurial), opening pull request to master (default), code-reviewing this pull request and merging it after review is finished</li>
</ul>
<p>Unfortunately Rhodecode does not allow to create pull request for Mercurial repository in case it contains any subrepo, even if there were no changes in that sub-repositories. </p>
<p>So that’s the main reason why we can’t use github flow with Rhodecode and that’s the reason why we have to Crucible. </p>
<p>I’ve shared these details with team about a year ago : <a href="https://rhodecode.tenderapp.com/help/discussions/support-tickets/1234-unable-to-create-pull-request" class="external">https://rhodecode.tenderapp.com/help/discussions/support-tickets/1234-unable-to-create-pull-request</a></p>
<p>Currently Rhodecode is more like a repository storage for us and while post-commit reviews are possible they are rarely used. That’s why most people at R almost never see Rhodecode web interface. </p>
<p>Let me know if you need any more details or have any workaround that would still allow us to use pull requests. </p>
RhodeCode CE/EE - Task #4235 (Resolved): Support GIT LFS serverhttps://issues.rhodecode.com/issues/42352016-09-19T16:45:28ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>It has been requested by few customers, and it's getting really mature. We should add support for GIT LFS server and support LFS via our HTTP backend</p>
<p><a href="https://github.com/github/git-lfs/wiki/Implementations" class="external">https://github.com/github/git-lfs/wiki/Implementations</a></p>
RhodeCode CE/EE - Task #4216 (New): [ux, renderers] implement consistent rendering for text fieldshttps://issues.rhodecode.com/issues/42162016-09-06T11:46:39ZLisa Quatmannlisa@rhodecode.com
<p>should be based on settings in _admin/settings/visual<br>
see parent ticket <a class="issue tracker-4 status-1 priority-2 priority-default parent" title="Task: [ux, renderering] Consistent formatting on text fields. (New)" href="https://issues.rhodecode.com/issues/4051">#4051</a></p>
RhodeCode CE/EE - Task #4051 (New): [ux, renderering] Consistent formatting on text fields.https://issues.rhodecode.com/issues/40512016-06-29T00:00:32ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Currently we have various fields formatted and wrapped in markdown formatters.</p>
<ul>
<li>For comments we use rst or MD formatter</li>
<li>For Commit messages we use urlify_commit_Message</li>
<li>for readme we use formatter based on the file extensions</li>
<li>for Pull requests we use Markdown/rst formatters</li>
</ul>
<p>Some of those formatters are inconsistent, ie commit messages vs commit commits. We need a quick iteration and find a subset that would make all those behave consistent.</p>
<p>Functionality within text fields which should be included:</p>
<ul>
<li>consistent formatting based on chosen renderer in _admin/settings/visual</li>
<li>@-mentions</li>
<li>issue tracker patterns</li>
<li>linkification of urls</li>
</ul>
RhodeCode CE/EE - Task #4003 (Resolved): User personal repository groups improvementshttps://issues.rhodecode.com/issues/40032016-06-09T13:14:30ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We have a concept of user namespaces/personal repository groups, they are personal repository groups that allows people to manage they own set of repos.</p>
<p>Current solution has some drowbacks:</p>
<ul>
<li><p>personal repo groups are linked by name, so a group marcink with owner marcink is marked as personal group of such user, if anything is renamed we lost the linking. <br>
We should introduce a database link instead. Add migration and add a flag that would mark such group as personal. Identifiing it by firstly OWNER and a flag.</p></li>
<li><p>we have to make sure personal repo groups cannot be revoked from yourself, only super-admins should allow to disconnect them. If i'm user marcink logged in i shouldn't be able to take out permissions for that group and have it innacessible for myself.</p></li>
<li><p>we should expose a link to personal repo group in dropdown under gravatar. So it will have now two entries <code>My account</code> <code>My repo groups</code> the second present if someone have a namespace, <br>
else it should be greyed out and not a link but still present</p></li>
<li><p>there should be a way to define a template for namespaces. A template string would be enough:</p></li>
</ul>
<p>user_namespace: /u/{username} (we should expose some other variables like {user_id} maybe {email})</p>
<p>This configurable via web-ifce would allow admin to define one permanent namespace, and each new user in the system would get his group under /u/</p>
<p>We at rhodecode put user namespaces under /u/ repo group, so for us to not have to move created repo group namespaces we need a template so each newly created one goes under the <code>/u/{username}</code>, a template could be used<br>
the Python String template similar how the clone URL template is made.</p>
<p>This basically solves a lot of problem for us under code.rhodecode.com since new users are not allow to create repos in top-level only in they own namespace, this concept confuses new people and they don't know where they could create forks for contribution.</p>
RhodeCode CE/EE - Task #3504 (In Progress): [routing] Move static assets under a common prefixhttps://issues.rhodecode.com/issues/35042016-04-18T17:03:42ZJohannes Bornholdjohannes@rhodecode.com
<p>If we move the static assets under a common prefix, we can way easier decide if a URL needs a license check or not.</p>
RhodeCode CE/EE - Task #2844 (New): Update Bcrypt to a maintained versionhttps://issues.rhodecode.com/issues/28442015-10-27T12:12:46ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We use py-bcrypt-0.4 which is unmaintained.</p>
<p>We should switch to <a href="https://pypi.python.org/pypi/bcrypt/3.1.1" class="external">https://pypi.python.org/pypi/bcrypt/3.1.1</a> which should be fully compatible.</p>
Documentation - Task #737 (New): What is an extra field and how do you add it?https://issues.rhodecode.com/issues/7372015-01-14T13:57:54ZLisa Quatmannlisa@rhodecode.com
<p>Ok, I know the answer to the first part but regular users may not. If you don't have any extra fields, then when you go to the page where you would edit them, you get a message which says "Extra fields are disabled". However, it has no information on how to enable them if one is able to do that.</p>