# Focused Browsing Dev Ops Brainstorming

###### tags: `Brainstorming` `Focused Browsing`

**June 10th, 2021**:
- We need a release script
- Need to seperate global styles from theme specific styles
- We need to create a pipeline that is structured in an organized way
- After doing some research on how deployments happen, I am seeing that a lot of times events get triggered everytime you push to the main branch
- Right now we have been making merge request straight to master, but it would be make sense if we start have our pipeline a bit more structured so we can do our deployments

Here is an example of a release process for an android app:


Here are some steps of how we can deploy properly to production:

- Here is the rest of the [article](https://itnext.io/how-to-automate-versioning-and-publication-of-an-npm-package-233e8757a526) that gives more details on these steps
- Of course instead of publishing an NPM package, this step would be replaced with publishing our chrome app to the extension store
- We can utilize tools like husky to run integration tests on our pushes and commits of our code
- To deploy to github, we can use actions where on every push to master, our release will be updated
- We need to have a yaml file to showcase the steps we need to take to do so

- Need to understand how we version our app properly, so that we can automate the versioning with the right standard in mind
- Automating our deployments to the chrome store:
- Here is a [video](https://www.youtube.com/watch?v=fH0jmBa-HhM) that runs through the steps of deploying to the chrome
- Here they used Travis CI for their CI/CD service but we can also use gitlab or github actions and run the same steps
- Here is the blog with the [steps](https://gokatz.me/blog/automate-your-chrome-extension-deployment-in-minutes/) that explains the process of how to write our release script to build our zip folders that need to be deployed to the store.