You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I previously used Gulp, but it feels outdated and started using Vite. I want to write logic using TypeScript and styles with Tailwind, or just SCSS. Vite handles compilation well and updates even the smallest changes in a fraction of a second using hot-reload.
I work with GitHub branches connected to Shopify:
• Main branch → Published theme
• Staging branch → Connected to Shopify as an unpublished theme
• Release branch → To join it all
• Develop branch → For ongoing work
The workflow is simple:
Working on develop.
Merging develop to release.
Run build on release.
Merging release to staging.
Preview it with the theme.
Merge release to main.
I'm not sure it is the best way. Especially when it comes to actualizing the dev branch. And when the customer did some changes in the main published theme.
Previously, when using Gulp, I would simply merge develop into staging, then into main, and the changes would sync. If there were modifications on the main, I would pull them back.
Do you have any good workflows or ideas on how to handle this? I like keeping things clean, optimized, and secure during deployment. I work mostly alone, sometimes with one person.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, I previously used Gulp, but it feels outdated and started using Vite. I want to write logic using TypeScript and styles with Tailwind, or just SCSS. Vite handles compilation well and updates even the smallest changes in a fraction of a second using hot-reload.
I work with GitHub branches connected to Shopify:
• Main branch → Published theme
• Staging branch → Connected to Shopify as an unpublished theme
• Release branch → To join it all
• Develop branch → For ongoing work
The workflow is simple:
I'm not sure it is the best way. Especially when it comes to actualizing the dev branch. And when the customer did some changes in the main published theme.
Previously, when using Gulp, I would simply merge develop into staging, then into main, and the changes would sync. If there were modifications on the main, I would pull them back.
Do you have any good workflows or ideas on how to handle this? I like keeping things clean, optimized, and secure during deployment. I work mostly alone, sometimes with one person.
Beta Was this translation helpful? Give feedback.
All reactions