Update GitHub desktop fork instructions
Why: The current fork instructions for Github desktop were out of date with the latest Github desktop.
Closes: https://github.com/desktop/desktop/issues/13165 (I realize this is an issue from a different repository, however in the comment thread of that issue you will see people mentioning that the issue arises because the docs here need updating.)
What's being changed (if available, include any code snippets, screenshots, or gifs): Minor documentation changes, inluding updating screenshots. The easiest way to see the changes would be to look at the PRs file changes.
Check off the following:
-
[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the 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
datadirectory.
- 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
-
[x] For content changes, I have completed the self-review checklist.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
đ Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:
- src/assets/lib/image-density.txt
You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process. :octocat:
The complete list of files we can't accept are:
- .devcontainer/**
- .github/**
- data/reusables/rai/**
- Dockerfile*
- src/**
- package*.json
- content/actions/deployment/security-hardening-your-deployments/**
We also can't accept contributions to files in the content directory with frontmatter type: rai.
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 |
|---|---|---|---|
desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md |
fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10 |
fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10 |
|
pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md |
fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10 |
fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10 |
|
get-started/exploring-projects-on-github/contributing-to-a-project.md |
fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10 |
fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10 |
from reusable |
fpt: Free, Pro, Team ghec: GitHub Enterprise Cloud ghes: GitHub Enterprise Server
@Nikkitory Thank you so much for opening this PR! ⨠I have filed an internal issue to fix this on our end, as this portion of the documentation will need to be updated by our team đ
Thanks again for raising a flag on this â¨
@Nikkitory Apologies for the confusion, but it looks like these changes may not need to be made internally đ I'm reopening this PR, and one of our team members will review shortly. Thank you!
A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days.
This PR has been automatically closed because there has been no response to to our request for more information from the original author. Please reach out if you have the information we requested, or open a new issue to describing your changes. Then we can begin the review process.
Would it be ok if I copied the head branch from here, made the requested changes, and created a new pull request?
@warp-core Please do! đ