[remote rejected] (refusing to allow an OAuth App to create or update workflow `.github/workflows/...` without `workflow` scope)

Github OAuth apps now require the 'workflow' scope when performing operations such as pushing a new workflow to a repo.

Github has started/added a new more fine-grained permissions for oauth.

Previously only the scope repo was needed to read/write access to a repo given permission- however now github also requires the workflow scope to be added. Without that, when you try to push / commit a Github action to a repo, you will see the new OAuth error:

[remote rejected] (refusing to allow an OAuth App to create or update workflow `.github/workflows/...` without `workflow` scope)

To allow your oauth app to make such requests, you request (and your app users accept) the additional scope workflow.

After updating your oauth app requested scopes, your oauth flow can/should redirect the user automatically , and Github will confirm to the user for permission for the additional change inscope:

Container Hosting is a fast, hassle free container hosting service.