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 #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 #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 #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 #5270 (New): Comments updateshttps://issues.rhodecode.com/issues/52702017-04-05T12:39:52ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Think about emails sent out on on comments:</p>
<ul>
<li>maybe they shouldn’t be inside both </li>
<li>add more context (TODO resolution)</li>
<li>Maybe thread that would allow reading those ?</li>
</ul>
RhodeCode CE/EE - Task #5200 (New): investigate search improvementshttps://issues.rhodecode.com/issues/52002017-02-08T00:59:38ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Search in changelog, proper repo filter, re-check syntax.</p>
RhodeCode CE/EE - Task #4669 (New): disable pytest sugar on nix-buildhttps://issues.rhodecode.com/issues/46692016-12-01T12:52:05ZMarcin 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>