Hi Oleksandr_K
Thank you for your response and the suggested alternatives. However , I strongly believe that these alternatives may not be suitable for our engineering team at scale. For instance, blocking other developers on Sisense or having one project per developer could significantly disrupt our collaborative workflow and affect our ability to meet sprint product deliverables effectively.
Furthermore, adopting one project per developer isn't feasible due to our reliance on a single Git repository for our Sisense project. It's important to emphasize that, given the nature of our work involving version control and GitHub, we expect robust collaboration and developer isolation features akin to those found in other engineering software solutions.
Therefore, I strongly believe that addressing this gap is imperative, as it has the potential to significantly impact our work and likely affects other clients who also rely on GitHub for collaborative development. Could you please consider prioritizing this feature request to ensure we can continue to work efficiently and effectively? Your support in addressing this issue would be greatly appreciated.
Thank you.
