-
Notifications
You must be signed in to change notification settings - Fork 583
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
Clarified "Team Name" in Migrate from Slack section #7711
base: master
Are you sure you want to change the base?
Conversation
Hello @AlexKalopsia, Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here. Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project. Please help complete the Mattermost contribution license agreement? This is a standard procedure for many open source projects. Please let us know if you have any questions. We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team. |
Newest code from AlexKalopsia has been published to preview environment for Git SHA 92d97cf |
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.
Thank you, @AlexKalopsia!! Very much appreciated!
@AlexKalopsia - I'll merge this correction as soon as an upstream issue with CLA checks is resolved. |
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
Summary
The documentation simply says that
<TEAM-NAME>
needed to be a single word.My team called "Team" is one word, so I just used that, which caused failure during the migration.
I eventually found out (via using
mmctl team list --json
) that I was using thedisplay_name
("Team") instead ofname
("team").I have clarified the documentation to prevent other users from running into the same issue.