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

Introduce CI and releases #419

Open
cynthia opened this issue Feb 9, 2023 · 1 comment
Open

Introduce CI and releases #419

cynthia opened this issue Feb 9, 2023 · 1 comment

Comments

@cynthia
Copy link
Member

cynthia commented Feb 9, 2023

It came to realization that 1) it is possible to break the build as our CI comes in too late, and 2) we have no change log or versioning the document. We should fix this.

#407

@LeaVerou
Copy link
Member

LeaVerou commented Feb 9, 2023

From our discussion in yesterday's breakout: we can use GitHub releases here, to make it easier to generate a changelog as a starting point (GitHub's "generate release notes" feature automatically pulls in all merged PRs, then we can edit from there).

That doesn't solve the CI issue of course. @plinss is of the opinion we should just use our own server, I think it's easier to use something like Netlify or even GitHub Actions so we don't have to worry about maintenance and server upgrades.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants