After logging in, when we open service and go to CICD tab, it is again asking for login. Even though this is happening first time only but its not something which is expected.
This is the issue with plugin @backstage/plugin-github-actions package.
We have used this package fetching, listing workflows. For access token, they have used scope as 'repo'.
On the other hand we use scope 'read:user' for access token.
As this change is from '@backstage/plugin-github-actions' package, used patch-package for the same (https://www.npmjs.com/package/patch-package). Created patch which run on postinstall.
Updated result:
Fixes # (issue)
Type of change
Please delete options that are not relevant.
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
[ ] Test A
[ ] Test B
Checklist:
[X] Performed a self-review of my own code
[X] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules
Extra login asked when asked when going into cicd and pull requests tabs
Same type of issue as -> ARC-117
Description
After logging in, when we open service and go to CICD tab, it is again asking for login. Even though this is happening first time only but its not something which is expected.
![image](https://github.com/sourcefuse/backstage/assets/109595269/ca155409-ed66-48b7-a5ff-9f1b8c1e6a33)
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: