Skip to content

Conversation

@sreepuramsudheer
Copy link
Collaborator

πŸ”© Description: What code changed, and why?

⛓️ Related Resources

πŸ‘ Definition of Done

πŸ‘Ÿ How to Build and Test the Change

βœ… Checklist

All PRs must tick these:

With occasional exceptions, all PRs from Progress employees must tick these:

  • Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
  • Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
  • Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
  • Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
  • Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

  • Tests added/updated? (all new code needs new tests)
  • Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

πŸ“· Screenshots, if applicable

@netlify
Copy link

netlify bot commented Aug 18, 2025

πŸ‘· Deploy Preview for chef-automate processing.

Name Link
πŸ”¨ Latest commit 3889dc1
πŸ” Latest deploy log https://app.netlify.com/projects/chef-automate/deploys/68a46be74191010008447d4a

Signed-off-by: sreepuramsudheer <[email protected]>
@sreepuramsudheer sreepuramsudheer force-pushed the ssudheer/chef_server_pipeline_fix1 branch from 9ced69f to 3889dc1 Compare August 19, 2025 12:19
@sreepuramsudheer sreepuramsudheer changed the title Ssudheer/chef server pipeline fix1 chef-server LTS changes. Aug 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants