RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042024-02-27T17:23:51ZRhodeCode - issues
Redmine RhodeCode CE/EE - Support #5713 (New): Deployment of Rhodecode on CentOS or Rocky Linuxhttps://issues.rhodecode.com/issues/57132024-02-27T17:23:51ZJean-Michel Mazzocco
<p>Hello </p>
<p>We need to rebuild a Rhodecode server due to OS obsolescence (CentOS 6) on version 4.27</p>
<p>I can see on configuration recommended only centOS 8 is supported.<br>
Our it team we propose to use a Linux machin with a fork of CentOS after the switch to stream, the rocky linux </p>
<p>I don't know if it's supported the current version of rocky Linux is the 9.3</p>
<p>Thank you </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 - Bug #5698 (Resolved): 5.0.0 release - documentation 4.X -> 5.X migration step-b...https://issues.rhodecode.com/issues/56982023-10-17T16:32:54ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>In order to smoothen the transition from 4.X release we need to write a guide how to move to 5.X series.</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 - Feature #5696 (New): Code Browser UIhttps://issues.rhodecode.com/issues/56962023-10-17T16:29:39ZMarcin 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 - Bug #5691 (Resolved): Fix 5.0.0 exceptionhttps://issues.rhodecode.com/issues/56912023-10-17T07:57:13ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p><a href="https://code.rhodecode.com/_admin/settings/exceptions/140374526066368" class="external">https://code.rhodecode.com/_admin/settings/exceptions/140374526066368</a></p>
<p>This seems to be a regression</p>
RhodeCode CE/EE - Bug #5684 (New): Integrations do not send through commits for new brancheshttps://issues.rhodecode.com/issues/56842022-07-27T22:50:57ZAndrew Whalan
<p>When pushing the first commit on a new branch, the commit information is not included in the resulting repo-push event.</p>
RhodeCode CE/EE - Bug #5682 (New): Login Page stuck until page is refreshedhttps://issues.rhodecode.com/issues/56822022-06-30T08:37:52ZEDV Habemus
<p>When logging in over the Web GUI, after the credentials are typed in, your're stuck on the login page until the page gets refreshed. <br>
Even after updating the issue keeps on happening.</p>
RhodeCode CE/EE - Bug #5672 (Resolved): Unable to browse git repository folders with # in nameshttps://issues.rhodecode.com/issues/56722021-12-16T16:00:28ZGreg Gaskill
<p>When browsing a git repository on our Rhodecode EE server web gui, we are unable to descend into folder whose names contain a # symbol.</p>
<p>An example browsing URI:</p>
<pre><code>https://example.com/projects/vendor/site/jobname/files/tip/Code/CP3%231?at=tip
</code></pre>
<p>Example error text for the above message says:</p>
<pre><code>error: There is no file nor directory at the given path: `Code/CP3` at commit xxxx
</code></pre>
<p>The actual folder name in the repository is "Code/CP#3"</p>
<p>Also note the actual rhodecode version running is 4.26 , not 4.24 (but the options didn't allow me to specify it)</p>
RhodeCode CE/EE - Bug #5670 (New): Repo-level administrators can usurp owner of repoistoryhttps://issues.rhodecode.com/issues/56702021-10-12T14:50:43ZYechen Qiao
<p>Not sure if this is a bug or a feature, but what I have found out is that any admins designated to be just a repo-level administrator (no repo group level admin and not super-admin), can modify the ownership of the repository to someone else. Even though in the access control page, the owners's rights looks unmodifiable.</p>
RhodeCode CE/EE - Bug #5664 (Resolved): Regression: When assigning permissions, cannot see own gr...https://issues.rhodecode.com/issues/56642021-07-14T13:27:04ZYechen Qiao
<p>Previously, if you are in group "A", and you own a project. When you try to assign permissions to project, group "A" is available for auto-complete.</p>
<p>Now, if you are not super-admin, do not have at least "Read" access to the group from some other group you also belong to, then when you try to assign your own group to a project, you will notice it is not available for selection at all in auto-complete. And it will clear itself out when you try to type the exact name before saving.</p>
<p>If the group owner tries to assign permission "Read" to its own group, the user gets an error message saying cannot assign group permission to the same group.</p>
<p>Right now, we are using workaround to use 2 groups instead of one for each group that can own a project, and we will have to manually add user of one group to its duplicate group when new users are added. Then with Group "B", I can assign "Read" to group "A", and if group "B" contains all members of group A, all members will now be able to add group A to the project.</p>
<p>Affected Version: 4.25.2 (not available for selection in this bug report page)</p>
RhodeCode CE/EE - Feature #5511 (New): New feature to synchronize the fork with the remote repo f...https://issues.rhodecode.com/issues/55112018-11-08T04:09:15ZArun Chandrasekaran
<p>This will be a very nice feature to have. Right now the users have to pull from the main repo and push to their personal forks.</p>
<p>If this feature is enabled, it will help them to synchronize their forks with ease.</p>
<p><img src="https://i.imgur.com/CoF9bVm.png" alt="New feature to synchronize the fork with the remote repo" /></p>
RhodeCode 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>