-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #92 from VenusCh001/doc-on-disk-partition
Doc on disk partition
- Loading branch information
Showing
8 changed files
with
120 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,55 @@ | ||
# Disk Partition Documentation | ||
|
||
## ⭐ Introduction | ||
|
||
Disk partitioning divides a hard drive into multiple logical storage units known as partitions. For example, local disk C: , D: etc. | ||
This documentation provides an overview of disk partitioning in the Windows operating system. | ||
|
||
![the disks](image-38.png) | ||
|
||
## ⭐ Advantages of Disk Partitioning | ||
|
||
1. Partitioning helps to organize data and system files | ||
2. Disk partitioning can improve system performance by segregating operating system files from user data, reducing disk fragmentation. | ||
3. It allows you to isolate sensitive data or specific applications, enhancing security by controlling access to different disk areas. | ||
4. It facilitates efficient backup and recovery processes. You can back up specific partitions without affecting others, making data restoration more targeted. | ||
5. It enables the creation of multi-boot systems, allowing you to install multiple operating systems on a single hard drive. | ||
|
||
## ⭐ Disadvantages of Disk Partitioning | ||
|
||
1. Partitioning involves manipulating disk structures, and errors during this process can lead to data loss if not done carefully. | ||
2. Resizing partitions can be challenging | ||
|
||
## ⭐ Methods of Disk Partitioning in Windows | ||
|
||
There are many methods for disk partitioning in Windows, but I will be writing about only one method which is very easy to perform, .e., Using disk management. | ||
|
||
1. Press `Windows icon + X` or go to the Windows search bar | ||
|
||
![window+x](image-33.png) | ||
|
||
2. select "Disk Management" for first option and type "disk management" for the second option. | ||
|
||
3. Right-click on the target drive | ||
|
||
![(disk management)Image from microsoft learn](image-34.png) | ||
|
||
4. Choose "Shrink" | ||
5. In the dialog box, edit the amount of space you want your new drive to occupy after shrink | ||
6. click on "shrink" option | ||
7. Now, unallocated space will be created | ||
8. Right click on the unallocated space | ||
9. Now click on "Create Simple Volume." | ||
10. a wizard will open | ||
|
||
![wizard](image-37.png) | ||
|
||
11. in the wizard, make changes such as choosing drive letter, volume labels, etc., and click on next again and again | ||
12. then, at last, click on "finish." | ||
13. you will get notification that "new drive is created". | ||
|
||
## ⭐ Parting Notes | ||
|
||
1. Disk partitioning is a powerful tool that offers various benefits but should be approached cautiously. Understanding the advantages, disadvantages, and available methods is essential for effective disk management in the Windows environment. | ||
|
||
2. Many users have both SSD and HDD drives then an advice from my side is that keep SSD for Local Disk C and make partition from HDD. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
# Git and GitHub Documentation | ||
📒Git is a versatile, open-source version control system designed to manage and track changes in software development projects of any size. | ||
📒GitHub is a web-based platform that provides hosting for software development projects. | ||
📒It offers a range of features to facilitate collaboration among developers. | ||
📒one can use git without github. | ||
📒one cannot use github without git. | ||
📒in this documentation we will be seeing git and github going hand in hand to support for the cause of the open source. | ||
|
||
Here's an overview of some key GitHub features and functionalities: | ||
|
||
## 1. Repository | ||
A repository, or "repo," is a container for a project on GitHub. It contains all the project files, including documentation, source code, and other assets like images,videos or textures(anything applicable). | ||
|
||
## 2. Commit | ||
A commit represents a snapshot of changes to a repository. Developers make commits to save their changes and create a history of the project's development. | ||
|
||
## 3. Fork | ||
Fork features allows us to have a copy of the original repository. This allows developers to freely experiment with changes without affecting the original project. Forks can be used for proposing changes to the original repository through pull requests. | ||
|
||
## 4. Clone | ||
Cloning a repository means creating a local copy of it on your machine. This allows you to work on the project offline and push changes back to the remote repository when ready. | ||
|
||
## 5. Branch | ||
Branches are sought of separate development area within a repository. Branches can later be merged back into the main branch. | ||
these are created so that there are no conflicts happening with the original codebase and the edited one. | ||
|
||
## 6. Pull Request | ||
A pull request is a proposal to incorporate changes from a forked repository or branch into the original repository. It provides a way for developers to discuss, review, and eventually merge changes. | ||
|
||
## 7. Push | ||
Pushing refers to uploading your local changes to the remote repository. This makes your commits accessible to others and updates the repository with your latest work. | ||
the changes made at your local machine and sent to remote repository is done using the push command | ||
|
||
## 8. Pull | ||
Pulling refers to fetching changes from a remote repository and merging them into your local repository. It allows you to stay up-to-date with the latest changes made by other developers. | ||
the changes made at the remote repository and sending to local machine is done through pull command | ||
|
||
## 9. Issues | ||
GitHub Issues provide a way to track tasks, enhancements, bugs, and other project-related topics. Issues can be assigned, labeled, and discussed, making them a valuable tool for project management. | ||
so one can create issues or work on the issues created by others(this is what happens in open source contributions isin't) | ||
|
||
## 10. Wiki | ||
The Wiki feature allows developers to create and maintain documentation directly within the GitHub repository. This can include project guides, FAQs, and other relevant information. | ||
|
||
## 11. Actions | ||
GitHub Actions enable automation workflows to be defined directly within the repository. These workflows can include tasks like testing, building, and deploying code. | ||
|
||
## 12. Insights | ||
GitHub provides various insights and analytics features to help you understand and manage your repositories effectively. Some key insights features include: | ||
|
||
- **Traffic:** View traffic data to understand how many visitors your repository is attracting. | ||
- **Contributors:** See a list of contributors and their commit activity. | ||
- **Commits:** Visualize the history of commits over time. | ||
- **Code Frequency:** Analyze the frequency of code contributions to identify active development periods. | ||
- **Pulse:** Explore the Pulse tab to see a summary of recent repository activity, including issues, pull requests, and commits. | ||
- **Graphs:** View graphs that show repository activity, code frequency, and contributors. | ||
- **Insights:** Access insights into your community's engagement and the health of your repository. | ||
|
||
### Parting notes | ||
#####(1) Best Practices | ||
- **Frequent Commits**: Make small, frequent commits to keep a detailed and manageable project history. | ||
- **Descriptive Commit Messages**: Write clear and concise commit messages to communicate the purpose of each change. | ||
- **Branch Naming Conventions**: Follow a consistent naming convention for branches to enhance project organization. | ||
|
||
**(2)** This documentation provides a brief overview of key GitHub features and functionalities For detailed usage instructions and best practices, refer to the [official GitHub documentation](https://docs.github.com/). |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.