github.com
to github.dev
, it will open a browser version of Visual Studio Code, called GitHub Code Spaces. You can even run dev environments directly from it, and do anything you'd be able to do locally.The process of making changes is as follows: create a fork of the repository, clone your fork, make changes on your repository, create a pull request, then the request will be reviewed and merged.
Here's a quickstart guide to forks. Let us know if you have any questions or need help getting that process going.
https://docs.github.com/en/get-started/quickstart/fork-a-repo
We'll also go over all this technical organizational stuff on Sunday. At the moment we are typing up these general workflow rules.The process of making changes is as follows: create a fork of the repository, clone your fork, make changes on your repository, create a pull request, then the request will be reviewed and merged.
Here's a quickstart guide to forks. Let us know if you have any questions or need help getting that process going.
https://docs.github.com/en/get-started/quickstart/fork-a-repo
We'll also go over all this technical organizational stuff on Sunday. At the moment we are typing up these general workflow rules. git clone https://<the URL of your fork>
Add changes, make commits...
then
git push
to add it to your fork. You should then be able to submit Pull Requests of your changes.
then when changes have been made upstream, Sync your fork with the upstream, by clicking "Sync fork" and then "Update Branch" on your fork's Github repo page.
then this to pull your updated fork back down to your machine:
git pull origin master
public/
directory, and manually inserting the data within the code. either one works for me, but like i said, my recommendation is using a CMS.
public/
directory, and manually inserting the data within the code. either one works for me, but like i said, my recommendation is using a CMS.