kbowers-ibm opened a new issue, #3773:
URL: https://github.com/apache/incubator-kie-tools/issues/3773

   **Description:**
   When importing a URL on KIE Sandbox that requires a connected user account, 
e.g. a private GitHub repository, the order you add the User accounts shouldn't 
matter, but does. At the moment when there are multiple connected GitHub 
accounts it only takes into account the one that was added first, when it 
should take all connected user accounts into consideration. As you can see 
below, the private repository requires access to the kbowers-ibm account and 
should have it, but only works when it's at the top of the connected accounts.
   
![Image](https://github.com/kiegroup/kie-issues/assets/92726146/fdd20e25-47e7-4c84-a7f2-50210fe4b6c5)
   
![Image](https://github.com/kiegroup/kie-issues/assets/92726146/49fc89b5-138e-4f6f-82c0-ee59d4c29c97)
   **Steps to Reproduce:**
   1. Go to https://sandbox.kie.org/#/
   2. Click on the User Icon at the Top right hand corner
   3. Click on Connect to an  account
   4. Click on Github and add a Personal Access Token
   5. Click Back 
   6. Click on Github and add a Personal Access Token to a 2nd GitHub account 
(one with a private repository)
   7. Navigate to the home screen and attempt to import a private repository 
from the 2nd GitHub account you added.
   8. Should get an error: "Can't determine Git refs for 'private repo URL'"
   
   **Acceptance Criteria:**
   - [ ] A user should be able to import a URL requiring an access token using 
any connected user account, regardless of the order it was connected.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to