-
Notifications
You must be signed in to change notification settings - Fork 566
Description
📜 Description
Currently it's a somewhat manual process to update the various tables we have in our docs, for example: #7540
The tables that should get updated are in these locations:
- https://github.com/backstage/community-plugins/blob/main/docs/README.md#workspaces-and-their-plugins
- https://github.com/backstage/community-plugins/blob/main/docs/compatibility/compatibility.md
- https://github.com/backstage/community-plugins/blob/main/docs/compatibility/new-frontend-system.md
👍 Expected behavior
It would be great if we had a GitHub action we could trigger on demand that would generate a similar PR as the above.
First we would need to update the list-compatibility and list-workspaces-for-docs scripts to work the same way as the list-feature script where it injects the results into the respective Markdown file.
Then these scripts could then be called in a GitHub action with a manual dispatch trigger and the results raised in a PR.
👎 Current Behavior
We have to manually generate the PR by running the various scripts which means we don't keep this informaiton as up to date as we should.
👟 Reproduction steps
N/A
📃 Provide the context for the Bug.
Not having this automated means we are likely to have stale content and/or missing items
👀 Have you spent some time to check if this bug has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else