8000 Better inform user about `workflow` permission by Abhi-Bohora · Pull Request #8613 · refined-github/refined-github · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@Abhi-Bohora
Copy link
Contributor

Closes: #8341
Related Sub Issue: #7641

In this PR I have added workflow scope to the token validation display and provided a clear error message with direct link to token settings.

Test URLs

Screenshot

without workflow permission
workscope_perm
with workflow permission
workflow_perm_enab

@fregante fregante added the meta Related to Refined GitHub itself label Aug 6, 2025
Comment on lines 267 to 268
8000
if ((apiResponse.message as string)?.includes('Personal Access Token')
&& (apiResponse.message as string)?.includes('without `workflow` scope')) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge these two checks or just include one. What's the full error?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @fregante even though the token doesn't have workflow scope only have repo and project scope it didn't trigger the workflow scope error. what I have tried is I made a PR with workflow file, It ran successfully without error and also I have tried discard changes from file changed view dropdown to see if that triggers workflow error, it didn't. It successfully ran and commits

@fregante fregante merged commit d7e8f9e into refined-github:main Aug 12, 2025
9 checks passed
@fregante fregante changed the title workflow scope detection display and Improved error message Better inform user about workflow permission Aug 12, 2025
@Abhi-Bohora Abhi-Bohora deleted the workflow-scope branch August 12, 2025 05:18
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

Development

Successfully merging this pull request may close these issues.

Consider showing whether personal token has workflow scope

2 participants

0