2.7 KiB
Contributing to PowerShell Documentation
Thank you for your interest in NTFSAccess documentation!
See below for details on how you can contribute to our technical documentation.
For general information about getting started with Git and GitHub, see GitHub Help.
Providing feedback on NTFSAccess documentation
Report errors, suggest changes, or request new topics by creating an issue on the NTFSAccess-Docs repository issues page.
Making minor edits to existing topics
To edit an existing file, navigate to it and click the “Edit” button. GitHub will automatically create your own fork of our repository where you can make your changes. Once you are finished, save your edits and submit a pull request to the staging branch of the NTFSAccess-Docs repository. After your pull request is created, someone on the NTFSAccess documentation team reviews your changes before merging them into the staging branch.
Making major edits to existing topics
If you are making significant changes, adding or changing images, or contributing a new article, you need to create a GitHub fork and clone it to your computer. A fork is a GitHub-based replica of the main repository, under your GitHub account, that provides you with a working copy which you can use in isolation. You create pull requests from your fork. Similarly, a clone is a local-based replica of the repository which, in this case, is a clone of your fork. The clone allows you to work on Git repositories offline, and using more powerful native software/tools.
Here is the workflow for making major edits to existing documentation:
- Create a fork of the NTFSAccess-Docs repository.
- Create a clone of your fork on your local computer.
- Create a new local branch in your cloned repository.
- Make changes to the file(s) you want to update in a Markdown editor.
- Push your local branch to your fork.
- Create a pull request to the staging branch of the NTFSAccess-Docs repository.