CHEF-25758 - standardize - Removing SLA from README#297
Merged
Conversation
Simplecov Report
|
|
|
clintoncwolfe
approved these changes
Sep 8, 2025
clintoncwolfe
approved these changes
Sep 16, 2025
Signed-off-by: Nandan Hegde <220186393+nandanhegde73@users.noreply.github.com>
Signed-off-by: Nandan Hegde <220186393+nandanhegde73@users.noreply.github.com>
nandanhegde73
force-pushed
the
nh/remove_sla_from_readme
branch
from
e3c0513 to
6899f6f
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request removes the oft-misleading Chef SLA text from the README.md file.
This action is being taken as part of the 2025 Repo Standardization Initiative.
As Progress Chef makes a best effort to respond to issues and pull requests in a timely manner, and prioritizes bugfixes and security updates on a customer-driven basis (which may span repos, or have no repo footprint at all), we no longer support the concept of a Service Level Agreement (SLA) on a repository-centric basis. For further details, see Repo SLA Removal FAQ.