private-chef-upgrade reference
Open
Nobody has claimed this yet.
Aspect: UX
Component: chef-server-ctl
Status: To be prioritized
Triage: Confirmed
Type: Chore
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
It's been a long time since any chef product was called "Private Chef". There's a reference to private-chef-upgrade in partybus.rb if someone wants to clean that up. Not sure what to change it to or I'd have made a PR.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in partybus.rb and inspect the private-chef-upgrade reference. Determine the current product wording from the repository context; done means the obsolete reference is replaced with an agreed term and the relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100