![github desktop forked repository github desktop forked repository](https://docs.github.com/assets/cb-54091/images/help/desktop/publish-repository.png)
This will help us identify what are you proposing in this change. On the bottom left, provide a summary/name for your commit. You will see the changes you made (files) listed on the left panel. Now that I have my sample in the folder, I can go back to GitHub Desktop: When a readme.md file is present with the correct content, someone navigating the folder structure on GitHub can read it in the browser. You can use a readme.md file from another folder as an example. MD files represent Markdown, which are very easy to write.
![github desktop forked repository github desktop forked repository](https://www.freecodecamp.org/news/content/images/2023/03/thumbnail-4.png)
The readme.md file is important and you should add to it the description of what your sample script is, what it does, and how to use it. I also created a readme.md file in this folder.I’m simply sharing this script with the repo, so all I have to do is to copy it. I copied the PS1 file from wherever it was before to this new folder.It’s important that you use a name for the folder that doesn’t exist yet, and is descriptive enough for anyone else looking at the samples. I created a new folder in the ITOpsTalk repo called “sample_abc”.The folder I’m using (as you can note from the header) is the one we cloned in the previous step.In this case, all we have to do is to create a new folder on the structure of the repo: In this example, we will use a fictitious PowerShell script – PS1 file – to exemplify how you can contribute to the repo. For now, let’s talk about how you make a contribution. Later we will cover how to open the PR from your fork to the original repo.įrom GitHub Desktop, you can also open a PR (if you’re ahead) or sync (if you’re behind). With that, select the option to use For my own purposes. We just anticipated that and created our fork already.
![github desktop forked repository github desktop forked repository](https://stefanscherer.github.io/content/images/2018/06/appveyor.png)
This is because you could clone the original repo, but you’d have to create a fork later if you made changes and want to open a PR. Next, GitHub desktop will ask how do you plan to use the fork. For example, if you cloned the original repo to C:\repos, you already have a folder with name ITOpsTalk in there. Make sure you are cloning the repo to a folder on your machine that has enough disk space, as well as doesn’t have another folder with the same name structure. This will launch the GitHub Desktop app, and present you with the option to clone the repo on your machine: Once you have GitHub Desktop set up on your machine, go back to the GitHub webpage with your account and forked repo, click the Code button and select Open with GitHub Desktop. To get started, download the tool, then open and log into it. This tool is a great option when you are not going to make code changes to existing scripts, like when you have a finished script and you just want to offer it to the ITOpsTalk repo. GitHub Desktop is a GUI app from GitHub that helps you manage the sync and other actions between repos and its copy on your machine. Here we will cover two scenarios: Making changes to the repo via GitHub Desktop or using Visual Studio Code on your machine. There are multiple ways to make edits/contributions to the repo, ranging from the most simple, to the more complex ones. Making contributions to the ITOpsTalk repo If you are behind, you can click the Sync fork option. If you are ahead, you can open a PR to contribute your changes to the original repo.It also informs you if your repo is behind (outdated) or ahead (you made changes to your fork) of the original repo.On the top left, you’ll see that the repo is now under your account, but it clearly shows that this is forked from the Microsoft/ITOpsTalk.When the process completes, it will take you to your own version of the repo in your account: Notice the Owner on the image above should be you. Once you have an account, make sure you are looged into it, then click the Fork button on the top right corner of the ITOpsTalk repo: If you made changes to the forked repo in your account, you could then open a PR to merge your edits with our repo.īefore anything, if you don’t have a GitHub account, go create one. The nice thing about it, is that the repo knows it has a source and compares the two repos – If your forked repo is behind/outdated, you can sync it so the content will match. When you fork a GitHub repo, you create a clone of that repo under your own user. This is necessary as only Cloud Advocates have writing access to this repo. The first step to contribute to the repo is to fork it to your own account. While the repository will be maintained by the Moder Infrastructure Cloud Advocates at Microsoft, you can also contribute with IT/Ops related samples by submitting a Pull Request (PR)! This blog post will cover how that process works, in case you are not familiar with using GitHub. This repo will feature Infrastructure samples for anything related to Azure Infrastructure, Hybrid, Windows Server, Containers, etc. A few days ago, we announced the launch of the ITOpsTalk repository on GitHub.