Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove warning about active development - Update edge.md #1602

Merged
merged 1 commit into from
Sep 25, 2023

Conversation

antongisli
Copy link
Contributor

Although edge is under active development, so is the rest of palette. the warning was written earlier in the year when edge was indeed under greater change, however now as it is maturing it isn't a good message for us to show while we are working on customer opportunities. This commit simply removes the warning box.

Describe the Change

This PR .....

Review Changes

💻 Add Preview URL

🎫 Jira Ticket

Although edge is under active development, so is the rest of palette. the warning was written earlier in the year when edge was indeed under greater change, however now as it is maturing it isn't a good message for us to show while we are working on customer opportunities. This commit simply removes the warning box.
@netlify
Copy link

netlify bot commented Sep 23, 2023

Deploy Preview for docs-spectrocloud ready!

Name Link
🔨 Latest commit 457ff67
🔍 Latest deploy log https://app.netlify.com/sites/docs-spectrocloud/deploys/650e36e9fb627700088d2e14
😎 Deploy Preview https://deploy-preview-1602--docs-spectrocloud.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 site configuration.

Copy link
Contributor

@ritawatson ritawatson left a comment

Choose a reason for hiding this comment

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

LGTM. I've added some backport labels for 4.0 and 3.4 and earlier. This means in addition to the standard merge, two additional merges are needed (manual merge) after checks pass for them - one for 4.0 and one for 3.4 and earlier.

@ritawatson ritawatson added documentation Improvements or additions to documentation backport-version-4-0 Backport change to version 4.0 auto-backport Enable backport backport-version-3-4 Backport change to version 3.4 labels Sep 25, 2023
@karl-cardenas-coding karl-cardenas-coding merged commit 14230eb into master Sep 25, 2023
12 checks passed
@karl-cardenas-coding karl-cardenas-coding deleted the antongisli-patch-2 branch September 25, 2023 16:22
@vault-token-factory-spectrocloud
Copy link
Contributor

💔 Some backports could not be created

Status Branch Result
version-4-0
version-3-4 Backport failed because of merge conflicts

You might need to backport the following PRs to version-3-4:
- docs: updated URLs to use file path context

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

backport --pr 1602

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@ritawatson
Copy link
Contributor

@karl-cardenas-coding and I discussed and decided this doesn't require a backport to 3.4 branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Enable backport backport-version-3-4 Backport change to version 3.4 backport-version-4-0 Backport change to version 4.0 documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants