-
Notifications
You must be signed in to change notification settings - Fork 328
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
Moving spo homesite
commands to spo tenant homesite
#6502
Labels
Comments
milanholemans
added
enhancement
needs peer review
Needs second pair of eyes to review the spec or PR
labels
Nov 24, 2024
What do you think @pnp/cli-for-microsoft-365-maintainers? |
sounds good to me. |
3 days is a decent response time if you ask me @Adam-it 😊 |
milanholemans
added
help wanted
and removed
needs peer review
Needs second pair of eyes to review the spec or PR
labels
Nov 27, 2024
Agreed |
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Dec 22, 2024
This was referenced Dec 22, 2024
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Dec 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since
spo homesite
commands are all using SharePoint administration APIs for which you have to be a SharePoint administrator, I wonder if we should deprecate them and rename them tospo tenant homesite
.In this case we should add
spo homesite
as alias for the new commands and remove them in the next major release.Todo: create v11 issue to remove the old aliases.
The text was updated successfully, but these errors were encountered: