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

build: set up CI #35

Open
mesqueeb opened this issue Oct 16, 2020 · 0 comments
Open

build: set up CI #35

mesqueeb opened this issue Oct 16, 2020 · 0 comments

Comments

@mesqueeb
Copy link
Member

mesqueeb commented Oct 16, 2020

develop on dev branch -- make dev the "main" branch

wishes for CI

  1. opening a PR to production (or even to dev) to run automated tests
  2. can only merge into production if automated tests passed
  3. automatic version increase (maybe like lerna a choice...? need to discuss)
  4. automatic release notes (based on commit messages)
  5. automatic deploy of documentation (firebase hosting, see https://firebase.googleblog.com/2020/10/preview-channels-firebase-hosting.html)
  6. automatic publish to npm
  7. automatic version added to Github releases with release notes (or link to changelog.md)
  8. automatic update of changelog.md

related

open questions

  1. Does npm workspaces help or bring more issues with package scopes?
    With lerna I always have issues with package scoping. Adding dev dependencies at root means you can't execute them in the package folder etc. Quasar project dependencies at root also caused a loot of issues when trying to build the quasar projects. Does npm workspaces bring new issues or will the fact that all packages are in a single node_modules folder at root be helpful.

  2. does npm workspaces replace lerna?
    Besides symlinking local packages to each other, lerna has the benefit of lerna deploy, which automatically increments all package versions throughout the local versions and dependencies, and automatically adds a "tag" with that version number on Github.
    Is NPM Workspaces to be used WITH lerna, or maybe we don't need lerna anymore since we're changing the whole CI pipeline anyway?

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

1 participant