-
GIT token access issue – use special API url !
GIT token access issue will usually be that You are using a wrong url. When accessing files through the GitLab API using an access token you must use a special API URL, not the regular browser URL you see in firefox when navigating the repository. Using the standard browser URL will not work with API authentication tokens. Why Use the API URL? The regular repository URLs are designed for web browsers and do not support token-based authentication. (They could, but they just don`t :)) The GitLab API requires you to call its specific endpoints, which accept access tokens and return the raw file data or JSON metadata. URL Comparison Parameter…
-
GitLab dev to qa merge conflict with no resolution options
GitLab dev to qa merge conflict with no resolution options can occur on multiple different occasions. One of the main reasons You can run into is : You can still check it out locally. The merge request You will be able to see and resolve in intellij or command line, whatever You fancy. At least you will be able to pull and just use the things that causes the conflic from QA. Unfortunetly it might require You to work on some changes again. For more stability i would do it one branch after the other so gitlab will not have issues when we first merge everything from QA using qa…
