Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark more clearly that the token is "required" #7231

Open
2 tasks
fregante opened this issue Jan 25, 2024 · 0 comments
Open
2 tasks

Mark more clearly that the token is "required" #7231

fregante opened this issue Jan 25, 2024 · 0 comments
Assignees
Labels
meta Related to Refined GitHub itself under discussion

Comments

@fregante
Copy link
Member

fregante commented Jan 25, 2024

Every so often someone is confused as to why some features don't work. Since features vary over time and occasionally start requiring the token, people are further confused as to why they stop working.

This makes no sense and I don't want to support token-less usage anymore. People can continue to use RG without it, but then we don't want to waste time figuring that out.

Why?

  • the token can be read-only and limited to public repos
  • our permissions already only target GitHub.com

Changes suggested:

  • Improve wording in options page to suggest the above
  • Show a block screen on the bug report page to invite people to use the token before opening an issue. I'm not sure if this screen can be made closeable (to allow people to report real bugs) or not (to block people from reporting token-related non-bugs)

Related:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Related to Refined GitHub itself under discussion
Development

No branches or pull requests

1 participant