Skip to content

Please add "Advanced Workflow Topics" section to "Github flow" document #44813

@Fran-B

Description

@Fran-B

Code of Conduct

What article on docs.github.com is affected?

https://github.com/github/docs/blob/main/content/get-started/using-github/github-flow.md

What part(s) of the article would you like to see updated?

The subject "Github flow" document does a good job of explaining the basic simple flow. However, concepts like Fork and Codespace, also exist along with a number of other more advanced things.

It would be helpful to provide links to the equivalent articles for each of those.

Being new to GitHub, I got to the subject document looking for information regarding how to "link" things together, etc. I expect that I am not the first. What I think I need is:

  • A Fork I think; because I need a linked branch/repo that has about 80% of it content removed, but I want to maintain linkage with the history of the main branch it was derived from. I only suspect a Fork is what I need and want to learn more.
  • A Codespace I think; because I need to create an application-repo that uses two of my repos and there are some complications that are not addressed by saying "also pull version X of this and that repo". So I want to learn what those are good for and how they can be used.

It is also likely that there are other concepts/features supported that might serve ones purposes to I would like see at least an "Other/Advanced Concepts" index where one can learn their names and read about what they are good for.

Additional information

Sorry if this is the wrong repo to report this issue against. It is where the linkage took me.

GitHub is large and there is a lot of useful information published here. I am finding it difficult to find what I want to learn about. The proposed "index" and "further subject reading" section could potentially be something added to the bottom of every page referenced by said index so that if say "Fork" is not really what you want, then you can find the "index" and see what else might be appropriate.

What I am thinking about is something like what Doxygen and Javadoc do for a list of classes. Just a "link name" and maybe very brief description of the concept.

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamtriageDo not begin working on this issue until triaged by the team

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions