You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue Description:
create_repo.py (python script) is not automated as mentioned in the readme.
Normally to connect a local repository to GitHub one has to go to the GitHub website, create a new respository and then add the new GitHub repo as a remote for your local repository. The create_repo script automates this process.
create_repo.py does ask for a prompt when linking the local repository with the remote repository. In this case, it defeats the purpose of automation.
Steps to Reproduce:
There might be various ways to reproduce the bug. I'm enlisting one of them.
Scenario (A):
Step 1:
Remove the stored credentials from the Windows credential manager if present.
Run the create_repo script with valid git configuration, valid arguments and with valid token in the github_secrets.py
Note: Due to the VScode extension it invokes GUI prompts else as shown below.
Thus, it is not automated as mentioned in the README.
Expected Behavior:
On create_repo execution, it should create a remote repository, create a local repository and link the local repository with the newly created remote repository without asking for a prompt. In linking the local repo with the remote repo it should use the credentials from github_secrets.py but not from the Windows credentials manager.
Current Behavior:
Current scripts work in the following scenarios.
The user has to explicitly provide the credentials in the prompt or,
It fetches the valid credentials from the Windows credentials manager.
Environment:
Device: Windows Laptop
Operating System: Windows 11
Software Version: git version 2.40.1.windows.1
Additional Information:
It is working fine for me, why?
In case it is working as expected then the following actions might be happening.
Users are using the same token which is cached (stored in the Win credentials manager). Thus by default, it uses the cached credentials instead of github_secreats.py 's token for linking the repos.
It need not be the scenario in the real use case.
Labels:
Bug
The text was updated successfully, but these errors were encountered:
Please @sahil-sagwekar2652 verify and review it from your end. In case it is a valid bug, I would like to work on this task. Thank you.
shubham-deshmukh
changed the title
Create repo automation failer : Fix the create_repo.py
Create repo automation failure : Fix the create_repo.py
May 24, 2023
Great work pointing out his bug @shubham-deshmukh . I will try to reproduce it locally and then get back to you. @tanish111 If you are up for it you can also try to reproduce the above mentioned bug on your system.
Issue Description:
create_repo.py (python script) is not automated as mentioned in the readme.
create_repo.py does
ask for a prompt
when linking the local repository with the remote repository. In this case, it defeats the purpose of automation.Steps to Reproduce:
There might be various ways to reproduce the bug. I'm enlisting one of them.
Scenario (A):
Step 1:
Note: Due to the VScode extension it invokes GUI prompts else as shown below.
Thus, it is not automated as mentioned in the README.
Expected Behavior:
On create_repo execution, it should create a remote repository, create a local repository and link the local repository with the newly created remote repository without asking for a prompt. In linking the local repo with the remote repo it should use the credentials from github_secrets.py but not from the Windows credentials manager.
Current Behavior:
Current scripts work in the following scenarios.
Environment:
Additional Information:
In case it is working as expected then the following actions might be happening.
github_secreats.py 's token for linking the repos.
It need not be the scenario in the real use case.
Labels:
Bug
The text was updated successfully, but these errors were encountered: