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
I have a Monorepo with the following folder structure:
apps/
|--app1/
|--app2/
:
:
|--app9/
Currently, my workflow triggers on every commit to the main branch, which is protected and requires PR reviews. Periodically, we run a semantic workflow that creates tags and releases.
While the current setup functions well, I prefer to refine it so that workflows trigger only when specific paths undergo changes. For instance, if app1 and app5 are modified, their respective jobs should run to deploy the application.
I can accomplish this easily using actions such as Paths-Filter and Changed-Files, particularly on the Main branch. However, I desire the same functionality in our production environment, which operates with semantic versioning. This complicates identifying changes and their corresponding paths on the releases/tags.
Although I could use git diff or other methods to achieve this, I prefer a streamlined workflow with minimal workarounds.
Any suggestions or best practices for handling this scenario will be appriciated.
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDQuestion
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
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
-
Select Topic Area
Question
Body
I have a Monorepo with the following folder structure:
Currently, my workflow triggers on every commit to the
main
branch, which isprotected
and requires PR reviews. Periodically, we run asemantic workflow
that createstags
andreleases
.While the current setup functions well, I prefer to refine it so that workflows trigger only when specific paths undergo changes. For instance, if
app1
andapp5
are modified, their respective jobs should run todeploy
the application.I can accomplish this easily using actions such as Paths-Filter and Changed-Files, particularly on the Main branch. However, I desire the same functionality in our production environment, which operates with semantic versioning. This complicates identifying changes and their corresponding paths on the releases/tags.
Although I could use
git diff
or other methods to achieve this, I prefer a streamlined workflow with minimal workarounds.Any suggestions or best practices for handling this scenario will be appriciated.
Beta Was this translation helpful? Give feedback.
All reactions