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

Update creating-a-new-organization-from-scratch.md #30804

Merged
merged 1 commit into from Jan 5, 2024

Conversation

carehart
Copy link
Contributor

Added link to related feature for transforming a personal account into an organization. Even if that may not be a common solution to this page's discussion of creating a new org, I propose adding this link because when one visits the Settings>Organizations page discussed in the steps here, a reader WILL see this option--but this page had no discussion of what that's about. The page I link to does detail the process (including pros and cons).

I'll understand if a maintainer seeing this might think it necessary to add some additional text content to add context for a reader here (creating a new org from scratch). Again, I just offer this to save people having to dig around (like I did) to find out what that "transform" option was about.

And it is a shame that while the settings page calls it "transforming" a personal account to an org, the title of the doc page instead is "Converting a user into an organization". But I used the autotitle feature here as that seems the preferred approach in these docs. I'll note propose a change to that page title, as that's a rabbit hole I don't want to go down.

Why:

See above

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adding just one doc link

Check off the following:

  • [x ] I will review my changes in staging, available via the View deployment link in this PR's timeline, once I can see that after creating this PR.

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • [x ] For content changes, I have completed the self-review checklist.

Added link to related feature for transforming a personal account into an organization. Even if that may not be a common solution to this page's discussion of creating a new org, I propose adding this link because when one visits the Settings>Organizations page discussed in the steps here, a reader WILL see this option--but this page had no discussion of what that's about. The page I link to does detail the process (including pros and cons). 

I'll understand if a maintainer seeing this might think it necessary to add some additional text content to add context for a reader here (creating a new org from scratch). Again, I just offer this to save people having to dig around (like I did) to find out what that "transform" option was about. 

And it is a shame that while the settings page calls it "transforming" a personal account to an org, the title of the doc page instead is "Converting a user into an organization". But I used the autotitle feature here as that seems the preferred approach in these docs. I'll note propose a change to that page title, as that's a rabbit hole I don't want to go down.
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team. label Dec 23, 2023
Copy link
Contributor

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md fpt
ghec
ghes@ 3.11 3.10 3.9 3.8 3.7
ghae
fpt
ghec
ghes@ 3.11 3.10 3.9 3.8 3.7
ghae

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

@nguyenalex836
Copy link
Contributor

@carehart Thanks so much for opening a PR! I'll get this triaged for review ✨

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review organizations Content related to organizations and removed triage Do not begin working on this issue until triaged by the team. labels Dec 26, 2023
@sophietheking sophietheking self-requested a review January 5, 2024 09:24
@sophietheking
Copy link
Contributor

@carehart Thanks for opening a PR and adding this link to the "Further reading" section, we really appreciate your contribution! I think your reasoning makes sense, so I'll go ahead and merge your PR. 👍

@sophietheking sophietheking added this pull request to the merge queue Jan 5, 2024
Merged via the queue into github:main with commit b79204a Jan 5, 2024
76 checks passed
Copy link
Contributor

github-actions bot commented Jan 5, 2024

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team organizations Content related to organizations waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants