yoshuawuyts/crossgen

CLI flag to regenerate GitHub token

Open

#10 opened on Sep 10, 2018

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Rust (5 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (20 stars)
PR merge metrics
 (PR metrics pending)

Description

Feature Request

Summary

Allow crossgen --regenerate-token to authenticate with GitHub again and generate a new token.

Motivation

If you delete the token from the GitHub UI but it's still cached on your system then crossgen will keep using that invalid token. Right now you have to hunt down the token and delete it to get crossgen to re-auth with GitHub.

Unresolved questions

Maybe it's possible to be smarter and check to see if the token exists over the GitHub API but I haven't looked into that

Contributor guide

Research direction
Examine the current token storage mechanism and authentication flow. Implement a new flag (e.g., regenerate token) that deletes the cached token and re authenticates with GitHub. Optionally, add a check to see if the token exists via GitHub API before deletion.
Tech stack
rust
Domain
cliauthentication
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75