Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: add roadmap page#552

Open
tomarra wants to merge 7 commits into
main from
feat/roadmap-page
Open

feat: add roadmap page #552
tomarra wants to merge 7 commits into
main from
feat/roadmap-page

Conversation

@tomarra

@tomarra tomarra commented Jun 8, 2026
edited
Loading

Copy link
Copy Markdown
Contributor

Status

READY

Description

Adding in a public roadmap page that is generated based on our Linear project list. This pulls any project that is labeled with the "Public Roadmap" label. This is regenerated on a nightly basis to ensure data is fresh and its done via Actions so the Linear API key is secured in GitHub Secrets and not exposed via a call on the client. There is also an option to just manually redeploy at any time as well via workflow dispatch.

This shows items going back one quarter and then forward looking as well as items that don't have a timeline targeted. This means that when we get to Q3 the Q1 items will magically be removed from this page in order to ensure it doesn't continue to grow indefinitely.

Note: Linear API keys are scoped to a user instead of an account. If we were to do the account level it would have to be a OAuth app which is way overkill here. This means the stored API key is currently tied to my account https://linear.app/docs/api-and-webhooks#api-keys

Preview Screenshot
CleanShot 2026年06月08日 at 11 54 02@2x

@nickshorebird nickshorebird left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider having a workflow create a PR and tagging a set of users to approve if changes are seen. This would hedge against someone accidentally having PII become public via a tag miss set. This would also separate the the actual doc updates from the roadmap doc update logic and could run on longer set schedule.

Comment thread src/pages/roadmap.astro

tomarra commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

Consider having a workflow create a PR and tagging a set of users to approve if changes are seen. This would hedge against someone accidentally having PII become public via a tag miss set. This would also separate the the actual doc updates from the roadmap doc update logic and could run on longer set schedule.

Since we are limiting what we are grabbing out of Linear I'm less concerned about the PII side of things (also there shouldn't be any PII in Linear in general). The PR thing is an interesting one I haven't thought about. Probably wouldn't be hard to do if we deem that to be useful.

nickshorebird reacted with thumbs up emoji

Copy link
Copy Markdown
Contributor

Consider having a workflow create a PR and tagging a set of users to approve if changes are seen. This would hedge against someone accidentally having PII become public via a tag miss set. This would also separate the the actual doc updates from the roadmap doc update logic and could run on longer set schedule.

Since we are limiting what we are grabbing out of Linear I'm less concerned about the PII side of things (also there shouldn't be any PII in Linear in general). The PR thing is an interesting one I haven't thought about. Probably wouldn't be hard to do if we deem that to be useful.

Sorry meant confidential not PII.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@nickshorebird nickshorebird nickshorebird approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /