-
Notifications
You must be signed in to change notification settings - Fork 102
Save and reuse repo credentials for private repos #800
Comments
hello @henriquemoraeszup, can i work on this? 😄 |
I've assigned you the issue @matheussn 👍🏼 |
Sorry for the delay, please go ahead! You have been an active contributor and we appreciate it! @matheussn would you be willing to have a chat with the team next week so we get your feedback on ritchie? |
Hello @henriquemoraeszup! These are my first contributions to Open Source projects. I am very happy to contribute to the project, and happier for the recognition! |
Wassup @matheussn! I will schedule 30min shortly. Also we have updated the user flow on the description on how this command should behave |
hello @matheussn, how are you? if you need any help i am on hand to assist in whatever is necessary. |
Hi! I did an implementation, but I didn't like some details hehehe 😄 |
@lucasdittrichzup Currently, I'm getting the token like this: I was thinking of creating a method to abstract the part of asking the user for the fields of standard credentials. Where I say "Create credential X" And regardless of the number of fields and types, he creates the structure for that credential. Some questions:
|
Would the set credential class help with this part @matheussn ? |
Yes, the idea would be to abstract the user input part of that class, so that I could use it in the add repo command. And don't use the |
There is the |
This issue has been automatically marked as stale because it hasn't had any activity in 60 days. It will be closed in 7 days if no further activity occurs (e.g. changing labels, comments, commits, etc.). Please feel free to tag a maintainer and ask them to remove the label if you think it doesn't apply. Thank you for submitting this issue and helping make Ritchie a better product! |
What would you like to be added:
When adding a private repo, the token is asked for every time. Ritchie could try to fetch the credential from the saved file. If there is no credential, prompt and save it
IMPORTANT: We should have a specific dedicated credential value for this token and In case a 401 is found (i.e.: user has more than 1 private repo requiring more than 1 different tokens), we should instruct the user about the fail and how he/she can proceed by either overwriting the current token or by switching to a new env
Why is this needed:
For better DevEx and so people do not need to regenerate private tokens every time they add a repo
The text was updated successfully, but these errors were encountered: