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

Add the workflow scope to the generated GitHub token #21587

Closed
Tracked by #21551
l0rd opened this issue Jul 26, 2022 · 0 comments · Fixed by eclipse-che/che-server#335
Closed
Tracked by #21551

Add the workflow scope to the generated GitHub token #21587

l0rd opened this issue Jul 26, 2022 · 0 comments · Fixed by eclipse-che/che-server#335
Assignees
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@l0rd
Copy link
Contributor

l0rd commented Jul 26, 2022

Is your enhancement related to a problem? Please describe

When trying to git push on GitHub (using the token generated by Che) changes to the .github/workflows folder I get this error (dogfooding instance):

To https://github.com/l0rd/che-blog
 ! [remote rejected] devfile-fixes -> devfile-fixes (refusing to allow an OAuth App to create or update workflow `.github/workflows/build-pr-check.yml` without `workflow` scope)
error: failed to push some refs to 'https://github.com/l0rd/che-blog'

Describe the solution you'd like

The token should include the workflow scope.

@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. area/che-server severity/P1 Has a major impact to usage or development of the system. labels Jul 26, 2022
@vinokurig vinokurig self-assigned this Jul 27, 2022
@svor svor modified the milestones: 7.51, 7.52 Jul 27, 2022
@svor svor mentioned this issue Jul 27, 2022
51 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants