Skip to content
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

Ecosystem CI build #190

Open
andywhite37 opened this issue Nov 7, 2019 · 0 comments
Open

Ecosystem CI build #190

andywhite37 opened this issue Nov 7, 2019 · 0 comments
Labels
type:discussion Discussion issues that should likely result in new actionable issues type:enhancement New feature or request

Comments

@andywhite37
Copy link
Member

andywhite37 commented Nov 7, 2019

Since we are starting to get more libs in the ecosystem, it would be nice to have a CI build that compiles all the libs at their latest versions whenever something changes.

We could setup a project like relude-ci or relude-packages, and npm install all the libraries we want (including any community libs), and then try to setup some automated workflow to submit pull requests for library updates, merge the pull requests to update the package.json, and run the CI build.

At one point we talked about seeing if the package-set concept would work (using purescript spago), but I don't think we want to take on that additional dependency at this time. I think we could get by with a simple repo that installs the versions and runs some builds.

@andywhite37 andywhite37 added type:enhancement New feature or request type:discussion Discussion issues that should likely result in new actionable issues labels Nov 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:discussion Discussion issues that should likely result in new actionable issues type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant