Uh oh!
There was an error while loading. Please reload this page.
Rfc for reusable workflows naming repository - #455
Conversation
sheplu
commented
Dec 16, 2025
@expressjs/express-tc to be reviewed. in itself that not blocking and can be changed quickly - just some extra time later one with changing that value everywhere :) |
blakeembrey
left a comment
There was a problem hiding this comment.
Going over the existing repos, we already have:
- https://github.com/expressjs/.github
- https://github.com/expressjs/secure-publish
- https://github.com/expressjs/tooling
- https://github.com/expressjs/ci-workflows
I'd be in favor of using .github, and tooling if there's consensus on avoiding .github for some reason, and delete the other two.
Finally, what about using one repo per workflow to make versioning simpler? This doc doesn't really address how you'd version workflows if they're all in one repo.
| This RFC proposes selecting an official repository name for hosting all shared and reusable GitHub Actions workflows used across the Express.js organization. | ||
| This RFC also proposes the creation of a new **Infrastructure Working Group (WG)** responsible for governing CI/CD standards, maintaining shared workflows, and ensuring consistent automation practices across all Express.js repositories. |
There was a problem hiding this comment.
Should this be part of this RFC? I think I'd block on this, I don't think we have enough "work" for a working group, but happy to be wrong.
Rfc for reusable workflows naming repository