-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: make roadmap issues mini dashboards #2520
chore: make roadmap issues mini dashboards #2520
Conversation
@@ -27,14 +27,34 @@ concurrency: | |||
jobs: | |||
update-workflow-issue: | |||
runs-on: ubuntu-latest | |||
strategy: | |||
matrix: | |||
label: ["jvm"] # add if desired: "codebase-health", "core", "infrastructure", "go", "security", "dx" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @TBD54566975/ftl-team if you want to automate your roadmap dashboards, you can opt in here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@worstell the dx
board is ready to go if you want use us as another test team for this :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wesbillman added dx
!
27beca6
to
0a6514f
Compare
0a6514f
to
fcfdef7
Compare
permissions: | ||
issues: write | ||
steps: | ||
- uses: actions/checkout@v4 | ||
with: | ||
fetch-depth: 1 | ||
- uses: cashapp/activate-hermit@v1 | ||
- run: update-workflow-issue | ||
- run: | | ||
declare -A label_to_issue_map=( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noice
@@ -1,4 +1,4 @@ | |||
name: Update roadmap issue #728 | |||
name: Update roadmap issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only concern here is that we might hit GitHub API limits, particularly when we're triaging and there's a flurry of activity.
If we start hitting issues I think we have some options, some basic optimisations are probably possible, and potentially combining all updates into a single script, merging some calls.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'll combine these into a single workflow for now, since the triggers are the same
@@ -0,0 +1,102 @@ | |||
#!/bin/bash | |||
|
|||
label="$1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we do a check for presence here and dump some usage info for anyone who runs it without args?
I was thinking too, that we should link to the individual team roadmaps from the main roadmap. |
fcfdef7
to
77ba88e
Compare
88b88e0
to
decb10a
Compare
decb10a
to
e6af23a
Compare
No description provided.