Conversation
Resolves merge conflict with infrahub-develop where specs is a symlink to dev/specs. Moves spec files to dev/specs/ and creates the symlink so both branches agree on the structure.
Deploying infrahub-sdk-python with
|
| Latest commit: |
55788b2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5fa6b1e8.infrahub-sdk-python.pages.dev |
| Branch Preview URL: | https://fix-move-specs-to-dev-symlin.infrahub-sdk-python.pages.dev |
WalkthroughRepository layout assumptions for feature specifications have been updated across multiple files. The primary change relocates the specifications directory structure from 🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
do we really need both |
The symlink from specs/ -> dev/specs/ was redundant. Remove it and update all path references in templates, scripts, and spec documents to use dev/specs/ directly.
@ajtmccarty there were quite a few references to |
specs/todev/specs/infrahub-developexpectsspecsto be a symlinkContext
PR #914 (merge develop → infrahub-develop) has a file/directory conflict:
infrahub-develophasspecsas a symlink todev/specs, whiledevelophas it as a real directory. This PR alignsdevelopwith the symlink convention.