In this screen image, since I am actually an administrator, I will get a button to merge the pull request, but regular users will see a slightly different page. The result will look somewhat similar to this: You can add additional information if you like as a message to the Change-HI administrators. You are "opening a pull request" on the official version of the repository, and requesting that the Change-HI administrators merge the changes in your branch into the official repo. Once you've committed your changes to your branch and pushed them to GitHub, you can browse to your GitHub repo and pull down the "Contribute" menu, which enables you to create a pull request:Ĭlick the "Open pull request" button, which brings up a page that looks like this: The actual process used depends upon whether you are doing local development or cloud-based development. The first step is to commit your change to your local repository and push those changes to GitHub. Let's say you have made some enhancements, and now you want to ask the administrators to incorporate this change into the official Change-HI site. Click "Create fork" which results in a new copy of the repo in your own personal account. You can see that this window selects my personal account, which is typically where you'll want the fork of the repository to go. Step Examples Fork the repo Ĭlick the "Fork" button in the top right of the page to bring up the fork window: Let's now provide examples for some of these steps. Update your fork so that it contains the most recent version of the Change-HI Morea site repository.At that point, the process is a bit simpler: Once the pull request is merged, you're done, at least until the next time you need to create another workshop (or update the materials associated with your original workshop). Sometimes, the administrators might request a few changes prior to merging, in which case you can easily update the file in the pull request. Create a pull request so that the Change-HI/EDU site administrators can review your changes prior to merging them into the published version of the site. Once you are satisfied with your changes, commit them and push your branch to GitHub.Edit files to update the site with your changes, and review the results. Now, create a branch to hold your changes to the site.Before making any changes, check your work by building and running your fork of the Change-HI/EDU Morea site (either locally or in the cloud).Depending upon your choice, Install a local morea development environment, or Install a cloud-based development environment.You might find Choose local or cloud development to be useful in making that choice. Decide whether you want to develop your site using the cloud-based Gitpod.io service, or locally.Create a fork of the most recent version of the Change-HI/EDU Morea site repository in your personal GitHub account.This means you will develop and maintain workshop curriculum using the following process: We would like to use a "Fork-and-Pull-Request" approach to development. There are many potential ways to support collaborative workshop curriculum development for HI-DSI. Getting started Our development process
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |