github-pull-request-board decouple board from entity page

[Sarabadu]

Hey, I just made a Pull Request!

Why

We would like to use the Pull request board inside of the Manage plugin page and there is some in progress work to show the PR data inside the home page too. but ro now the plugin requires to be inside the EntityProvider context scope.

What

On this PR we are decoupling the EntityProvider from the rest of the board query and views.

Changes:

• Removing the useEntity from the useUserRepositoriesAndTeam hook, and accepting one or more Entities
• Create new component that accepts Entities and shows the Pull Request board for all the passed groups
• Add the dev folder to have some better way to test it locally
• Move refactor and add some tests

The existen componentes should not get affected by this change but we are exporting a new React component to be posible to use in other places

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)
• All your commits have a Signed-off-by line in the message. (more info)

[backstage-goalie]

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
@backstage-community/plugin-github-pull-requests-board	workspaces/github-pull-requests-board/plugins/github-pull-requests-board	patch	v0.8.0

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[Sarabadu]

Not stale

[awanlin]

Thanks for the contribution @Sarabadu, left one comment but overall looks good to me 👍

[BethGriggs]

I'm not familiar with this plugin, does this mean it is always derived from the first entity? Perhaps that is intentional?

[Sarabadu]

thanks, yes is intended, that field is used on the current EntityPage, that has always only 1 entity.

in the future if multiple organization tracking is needed i think it would be better to make a bigger refactor to decouple it a bit more, but as it now I tried to no go full down in the rabbit hole

[BethGriggs]

LGTM, assuming review comments considered. Dropping an a approving so this isn’t blocked while I’m OOO.

[Sarabadu]

@awanlin, if you have some time, we still need your approval after the change request

[awanlin]

Let get this out