-
Notifications
You must be signed in to change notification settings - Fork 3
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
(#2) Adds Initial Examples #3
Conversation
deployments/upgrading-chocolatey-for-business-clients/README.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also think we need a complete review of these files to ensure that we are consistent in usage of:
- Deployment Plan
- Deployment Step
etc.
deployments/upgrading-chocolatey-for-business-clients/Deployment-Latest1x.json
Outdated
Show resolved
Hide resolved
deployments/upgrading-chocolatey-for-business-clients/Deployment-Latest2x.json
Outdated
Show resolved
Hide resolved
9b135a5
to
ed26e17
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deployments should be Deployment Plan or Deployment Steps. Both, along with Target Groups, are names of things and should be capitalized.
@JPRuskin It looks like you've got everything fixed up here. Can you tidy up the commits on this PR and then we can merge it? |
@steviecoaster The README.md file needs to be updated with similar changes to the rest of the doc. I can't provide any comments on that, I'm assuming because GitHub is seeing it as a binary file. |
6d16447
to
ec483f4
Compare
As I mentioned, I can't provide any comments on the README.md file, so I'll add them here.
|
deployments/upgrading-chocolatey-for-business-clients/README.md
Outdated
Show resolved
Hide resolved
ec483f4
to
ba57c09
Compare
FWIW, this should be sorted in all future PRs. Just this one where we're going from the template's UTF16 to UTF8 (like all our other md using repos, as far as I can tell). Hopefully all of the above have been addressed, now. |
Adds a basic readme with lightweight instructions on importing any old Deployment Plan, along with a friendly "please feel free to contribute" note.
I have personally verified all requested changes have been made
5e996dd
to
c8a9b05
Compare
I have personally verified all requested changes
This commit adds the initial examples to the repository. Also updates to "Deployment Plans" rather than "Deployment(s)"
c8a9b05
to
3a0f98a
Compare
Description Of Changes
Adds an initial readme and some example deployments to the repository.
Motivation and Context
These examples can be displayed and linked to on our docs page, referred to by teammembers, or contributed to by community members.
Testing
Operating Systems Testing
N/A
Change Types Made
[ ] Bug fix (non-breaking change).[ ] Breaking change (fix or feature that could cause existing functionality to change).[ ] PowerShell code changes.Change Checklist
This needs to be merged before the documentation can link to it.
[ ] Tests to cover my changes, have been added.[ ] All new and existing tests passed?[ ] PowerShell code changes: PowerShell v2 compatibility checked?Related Issue
Fixes #1
Resolves #2