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

Rename options. Closes #4467 #5225

Closed
wants to merge 9 commits into from
Closed

Conversation

Saurabh7019
Copy link
Contributor

Closes #4467

@Saurabh7019 Saurabh7019 marked this pull request as ready for review July 15, 2023 19:38
@milanholemans
Copy link
Contributor

Awesome job @Saurabh7019! We'll try to review it ASAP!

Copy link
Contributor

Choose a reason for hiding this comment

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

On first sight, one thing I noticed is that you update the options from our sample scripts, which is fantastic, but we should also update the version of it to v7.0.0 in the metadata JSON file located in the assets folder.

@milanholemans
Copy link
Contributor

Also, because v7 is a new major version, we create an upgrade guidance for it. In this PR we should include a section on what users should do to upgrade their v6 script to v7.
Could you include this upgrade guidance in your PR as well? You can get some inspiration here: https://pnp.github.io/cli-microsoft365/v6-upgrade-guidance#aligned-options-with-naming-convention

I know it's your first major version so I don't blame you at all, just know that every v7 PR is supposed to update this page.

@Saurabh7019
Copy link
Contributor Author

Could you include this upgrade guidance in your PR as well

Sure!

[spo listitem attachment list](./cmd/spo/listitem/listitem-attachment-list.mdx)|`itemId`|`listItemId`
[spo user get](./cmd/spo/user/user-get.mdx)|`loginName`|`userName`


Copy link
Member

Choose a reason for hiding this comment

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

Let's remove this unnecessary empty line

@milanholemans milanholemans linked an issue Jul 18, 2023 that may be closed by this pull request
30 tasks
@milanholemans
Copy link
Contributor

milanholemans commented Jul 22, 2023

Hi @Saurabh7019, we did another v7 release do your PR got messed up. Could you rebase with the latest v7 branch to fix the conflicts?

If you encounter any problems, please reach out to us.

Thanks!

@milanholemans milanholemans marked this pull request as draft July 23, 2023 12:53
@milanholemans milanholemans self-assigned this Jul 23, 2023
@milanholemans milanholemans added the pr-major PR for the next major release label Jul 23, 2023
@Saurabh7019 Saurabh7019 marked this pull request as ready for review July 24, 2023 08:07
Copy link
Contributor

@milanholemans milanholemans left a comment

Choose a reason for hiding this comment

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

Great work! Made 2 small adjustments while merging.

Copy link
Contributor

Choose a reason for hiding this comment

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

Since this is something that's incorrect in our docs at this moment. Let's fix it in another PR and merge it with main branch.

@@ -22,7 +22,7 @@
"metadata": [
{
"key": "CLI-FOR-MICROSOFT365",
"value": "6.3.0"
"value": "v7.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's drop the v before the version number.

@milanholemans
Copy link
Contributor

Manually merged. Thank you for the great work! 👏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-major PR for the next major release pr-merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rename options
6 participants