Skip to content

Conversation

@sheplu
Copy link
Member

@sheplu sheplu commented Dec 3, 2025

Rfc for reusable workflows naming repository

@sheplu
Copy link
Member Author

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 :)

Copy link
Member

@blakeembrey blakeembrey left a comment

Choose a reason for hiding this comment

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

Going over the existing repos, we already have:

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.
Copy link
Member

Choose a reason for hiding this comment

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

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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants