RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042023-12-07T08:07:42ZRhodeCode - issues
Redmine RhodeCode CE/EE - Task #5712 (New): add framework to set some UI settings via .ini file for easie...https://issues.rhodecode.com/issues/57122023-12-07T08:07:42ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Currently there's a distinction on what can be controlled via .ini file vs DB.</p>
<p>some of the options seems to not make sense to be controlled via UI (like svn proxy)</p>
<p>Add a framework so you cna still controll this via .ini, but it will save the value in DB and in case this is defined in .,ini file make it read-only on UI.</p>
<p>e.g if svn.proxy is set in ini, push this value into the DB, and make it read-only in DB.</p>
<p>Tis would greatly simplify deployments on k8s or other docker stacks</p>
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 #5705 (New): 5.X - activate update task automatically over rcstackhttps://issues.rhodecode.com/issues/57052023-11-13T08:06:05ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Because rcstack has enabled scheduler by default, we should activate the periodic update check</p>
RhodeCode CE/EE - Task #5701 (Resolved): Default permissions cache purgehttps://issues.rhodecode.com/issues/57012023-11-06T07:17:38ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>It looks like the cache purging for global default permissions aren't pushed once the override function is set.</p>
<p>make sure the flush permissions caches once this is enable. Probably we need to rebuild the full set up permissions in order for this to work</p>
RhodeCode CE/EE - Task #5697 (New): Improve CI & CD integrationshttps://issues.rhodecode.com/issues/56972023-10-17T16:31:20ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5695 (New): Artifacts - Making artifacts a prime functionalityhttps://issues.rhodecode.com/issues/56952023-10-17T16:28:43ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5694 (New): GIT LFS 2.0https://issues.rhodecode.com/issues/56942023-10-17T16:27:54ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5537 (Resolved): Add owner to create_pull_request APIhttps://issues.rhodecode.com/issues/55372019-02-13T10:44:04ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Similar like:<br>
<a href="https://code.rhodecode.com/rhodecode-enterprise-ce/files/fd4b2bf5348f1def66ac9495be06eac1e60f8fae/rhodecode/api/views/repo_api.py#L562" class="external">https://code.rhodecode.com/rhodecode-enterprise-ce/files/fd4b2bf5348f1def66ac9495be06eac1e60f8fae/rhodecode/api/views/repo_api.py#L562</a><br>
<a href="https://code.rhodecode.com/rhodecode-enterprise-ce/files/fd4b2bf5348f1def66ac9495be06eac1e60f8fae/rhodecode/api/views/repo_api.py#L640" class="external">https://code.rhodecode.com/rhodecode-enterprise-ce/files/fd4b2bf5348f1def66ac9495be06eac1e60f8fae/rhodecode/api/views/repo_api.py#L640</a></p>
<p>We should expose this to create_pull_request.</p>
<p>ps. We should maybe check all other API functions and make this type of functionality consistent across all create_ type function</p>
RhodeCode CE/EE - Task #5404 (New): Add an option to detach review rules when deleting an userhttps://issues.rhodecode.com/issues/54042017-11-22T11:23:48ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>In cases there are 100s, and user should be removed we need an explicit option to detach an user from review rules.</p>
<ul>
<li>check what happens then to the old review get changed</li>
<li><p>big fat warning about how it can change old ?</p></li>
<li><p>maybe a replace with X user ?</p></li>
</ul>
<p>again reconsider what this means and if we really should have it !</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 #5386 (Resolved): Increase security for Email Changehttps://issues.rhodecode.com/issues/53862017-09-13T10:34:51ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We already require OLD password when changing the current user password, but email is another way to recover an account. If hacker is able to access open instance of RC he can trigger an email change and change the password after that.<br>
Proposed idea to fix this is:</p>
<ul>
<li>Make email a select field instead of text input</li>
<li>Inside the input we allow user to pick any of the addresses added via extra emails</li>
<li>In order to change an email user needs to add a new email from additional emails, this needs to require a password, and then he can select a new email from the entry.</li>
</ul>
<p>THis should force users to give current password to change the email</p>
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 #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>