Add workflow to automate component status board updates #1672
Conversation
|
size-limit report 📦
|
|
Hmm, do you know why the package-lock got a lot smaller? |
…rimer/react into feature/component-status-project-board
Found the issue. package-lock was generated using v1, when it should be v2. Should be sorted now.
Thanks @colebemis. Lint issues fixed now. Going to merge later today, in case there's any other feedback coming. |
tsconfig.json
Outdated
| @@ -16,5 +16,5 @@ | |||
| "forceConsistentCasingInFileNames": true, | |||
| "typeRoots": ["./node_modules/@types", "./@types"] | |||
| }, | |||
| "include": ["@types/**/*.ts", "src/**/*.js", "src/**/*.ts", "src/**/*.tsx"] | |||
| "include": ["@types/**/*.ts", "script/**/*.ts", "src/**/*.js", "src/**/*.ts", "src/**/*.tsx"] | |||
There was a problem hiding this comment.
Can you confirm that we're not accidentally publishing script/** type declaration files to the npm package?
There was a problem hiding this comment.
component-status.json won't appear in the package, as it's ephemeral to its own isolated workflow. This can be verified in the canary release here.
@colebemis, the d.ts files are back now too. Had to add the scripts folder to tsconfig.build.json
…rimer/react into feature/component-status-project-board
Summary
Adds a new Actions-based workflow to automatically organise Component cards, along with their corresponding lifecycle status on a new Component Status project board.
Demo
See it in action here: https://github.com/primer/react/projects/5
This automation functionality was requested by LT, and deploys alongside our docs component status page. They both share the same data source so maintaining this board will require no additional overhead.
Big thanks to PVC team for creating the card upsert script. I've adapted it to work for our PRC project in this PR.
Contributes to https://github.com/github/primer/issues/339
Screenshots
PRC board:
PVC board for reference:
Merge checklist