Right now we currently have another branch to support bitbucket pipelines. I think we could come across other pipeline environments when moving across in our careers.
Currently support
[x] GitHub CI *
[ ] Bitbucket Pipelines (doesn't support app deployment ATM)
Nice to have are:
[ ] Azure Pipelines
[ ] GitLab?
* = Base pipeline that all other pipelines should at least mirror in their processes. Minimally, the pipeline should build and lint workspaces, build Storybook if there is one.
These separate configurations should have their own branch and should be synced up with main when changes are pushed. For example, check out .github/workflows/bitbucket.yml and the bitbucket branch, which gets triggered on every push to main. Pushing to a another remote repo is optional, unless pipeline triggers need to happen that way.
Right now we currently have another branch to support
bitbucket
pipelines. I think we could come across other pipeline environments when moving across in our careers.Currently support
Nice to have are:
* = Base pipeline that all other pipelines should at least mirror in their processes. Minimally, the pipeline should build and lint workspaces, build Storybook if there is one.
These separate configurations should have their own branch and should be synced up with
main
when changes are pushed. For example, check out .github/workflows/bitbucket.yml and the bitbucket branch, which gets triggered on every push tomain
. Pushing to a another remote repo is optional, unless pipeline triggers need to happen that way.Related issues: https://github.com/psychobolt/vite-storybook-boilerplate/issues/123