I am trying to start using the linear-release in a monorepo and do the first sync, so I am basically calling linear-release --verbose --include-paths="lapi/**" with subproject-specific LINEAR_ACCESS_KEY, but it fails to find any changes. Yes, there are commits touching different directories. The output is:
linear-release v0.11.2
Using CLI --include-paths: ["lapi/**"]
No recent releases found; assuming first sync
Inspecting current commit only
No commits found between b529897..b529897 with paths: lapi/**
Found 0 commits between b529897 and b529897
No commits found matching ["lapi/**"]. Skipping release creation.
It checks just single commit and founds nothing. When I try it for the subproject actually beaing touched by the last commit, I get:
linear-release v0.11.2
Using CLI --include-paths: ["courier-api/**"]
No recent releases found; assuming first sync
Inspecting current commit only
Found 1 commit between b529897 and b529897
Debug sink: {
"inspectedShas": [
"b529897a1c6fd9b2a6f94bdce12b3687cd6a8ae0"
],
"issues": {},
"revertedIssues": {},
"pullRequests": [],
"includePaths": [
"courier-api/**"
]
}
Synced to release b529897 (version: b529897): no new issues or pull requests
And now it does not show any changes to the project. How is this supposed to work actually? I would like to have some issues inside the first release and I am completely fine with supplying my own starting commit to allow scanning for changes.
In a different monorepo, we were moving multiple projects into the monorepo recently, so the commit SHAs detection for previous release will break for linear-release - we used git rewrite to move projects into subdirectories, so the new monorepo has different commit SHAs. This use case (the release already created previously, but in incompatible repository) would also benefit from the option to override the previous-release commit SHA.
I am trying to start using the
linear-releasein a monorepo and do the firstsync, so I am basically callinglinear-release --verbose --include-paths="lapi/**"with subproject-specificLINEAR_ACCESS_KEY, but it fails to find any changes. Yes, there are commits touching different directories. The output is:It checks just single commit and founds nothing. When I try it for the subproject actually beaing touched by the last commit, I get:
And now it does not show any changes to the project. How is this supposed to work actually? I would like to have some issues inside the first release and I am completely fine with supplying my own starting commit to allow scanning for changes.
In a different monorepo, we were moving multiple projects into the monorepo recently, so the commit SHAs detection for previous release will break for
linear-release- we used git rewrite to move projects into subdirectories, so the new monorepo has different commit SHAs. This use case (the release already created previously, but in incompatible repository) would also benefit from the option to override the previous-release commit SHA.