Skip to content

Repo: Onboard OctoGuide #11203

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

Open
JoshuaKGoldberg opened this issue May 12, 2025 · 0 comments
Open

Repo: Onboard OctoGuide #11203

JoshuaKGoldberg opened this issue May 12, 2025 · 0 comments
Labels
blocked by another issue Issues which are not ready because another issue needs to be resolved first blocked by external API Blocked by a tool we depend on exposing an API, such as TypeScript's Type Relationship API repo maintenance things to do with maintenance of the repo, and not with code/docs

Comments

@JoshuaKGoldberg
Copy link
Member

JoshuaKGoldberg commented May 12, 2025

Suggestion

We use a few "pure" (no repo JS/TS code) GitHub Actions / workflows for repo management:

Both of these general areas of management are part of OctoGuide. OctoGuide also has a few more rules that flag other common points. I'd like to switch us over to OctoGuide so that we just have the one unified action for these things.

Additional Info

Blocked on a couple points:

a11y-alt-bot.yml does not re-run on issue_comment edited events because netlify and nx bots frequently update comments. This isn't a blocker for enabling OctoGuide because we can keep that intentional omission. Just noting here. Also relevant for improving CI times: #11204

Disclaimer: I made OctoGuide (in part from having to set these things up manually here!). I asked internally if folks were ok with this and nobody said anything against it. But, you know, full disclaimer.

💖

@JoshuaKGoldberg JoshuaKGoldberg added triage Waiting for team members to take a look repo maintenance things to do with maintenance of the repo, and not with code/docs labels May 12, 2025
@JoshuaKGoldberg JoshuaKGoldberg added blocked by external API Blocked by a tool we depend on exposing an API, such as TypeScript's Type Relationship API blocked by another issue Issues which are not ready because another issue needs to be resolved first and removed triage Waiting for team members to take a look labels May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked by another issue Issues which are not ready because another issue needs to be resolved first blocked by external API Blocked by a tool we depend on exposing an API, such as TypeScript's Type Relationship API repo maintenance things to do with maintenance of the repo, and not with code/docs
Projects
None yet
Development

No branches or pull requests

1 participant