Skip to content

Conversation

@lapentad
Copy link
Contributor

Replacing #261

@nephio-prow nephio-prow bot requested review from arora-sagar and henderiw October 17, 2025 09:41
@lapentad lapentad requested review from Catalin-Stratulat-Ericsson and efiacor and removed request for arora-sagar and henderiw October 17, 2025 09:41
@lapentad lapentad changed the base branch from porch-docs-refactor to main October 20, 2025 08:12
@lapentad
Copy link
Contributor Author

Rebased on main

@nephio-prow
Copy link
Contributor

nephio-prow bot commented Oct 21, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lovesprung for approval by writing /assign @lovesprung in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@netlify
Copy link

netlify bot commented Oct 21, 2025

Deploy Preview for nephio ready!

Name Link
🔨 Latest commit ca86066
🔍 Latest deploy log https://app.netlify.com/projects/nephio/deploys/691b41ebcd00020008702db0
😎 Deploy Preview https://deploy-preview-275--nephio.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@nephio-project nephio-project deleted a comment from netlify bot Oct 21, 2025
@lapentad lapentad force-pushed the tutorial-upgrades-section branch from e1e16be to 64b4a4a Compare October 29, 2025 12:10
@lapentad lapentad force-pushed the tutorial-upgrades-section branch from 64b4a4a to 85b2a82 Compare October 29, 2025 12:16
@lapentad
Copy link
Contributor Author

Rebased

Signed-off-by: lapentafd <[email protected]>
* **Separate Repositories:** For better organization and access control, keep blueprint packages and deployment packages in separate Git repositories.
* **Understand Your Strategy:** Before upgrading, be certain which merge strategy fits your use case to avoid accidentally losing important local customizations. When in doubt, the default `resource-merge` is the safest and most intelligent option.

### Cleanup
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice to have but prob not necessary.

Signed-off-by: lapentafd <[email protected]>
Signed-off-by: lapentafd <[email protected]>
Signed-off-by: lapentafd <[email protected]>
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants