Source control:

In order to save your changes you need to commit these changes in vscocde which will connect to your github whcih connects to website where it makes the those changes and you either can create pull request git pull or commit

sourcecontrol.png

Forking:

To create a fork on GitHub, visit the repository’s page, click the “Fork” button’s dropdown arrow, select “Create New Fork,” and then proceed. After forking, you can create pull requests to contribute changes, or use the “Use this template” option to make your repository independent from the original.

exampleofForkingarepo.png

Branching:

In your repository, you can create branches to make changes without affecting the main branch. Branches are useful for testing features before merging them into the main branch. When working in a team, branches allow each member to work in their own space and integrate their contributions later.

howtocreateabranch.png

Building:

After installing all your tools and getting them ready, open a new terminal in VS Code to type in commands. If there’s no virtual environment (Venv) directory, run source venv/bin/activate inside the terminal. This should be done in the Windows terminal before running code . To build your site, use the make command.

  • Error Fixes: If you encounter errors, here are some solutions:
    • Run bundle install to install necessary dependencies.
    • Ensure all tools are installed correctly by checking their versions.
    • Verify that no files have incorrect names, such as spaces or duplicate names.
    • Reinstall tools if needed.

example of building.png

ubuntueg.png

Testing:

After running make in order to be condfident go to inspect element go to console if it pops up error look inside code as it tells you where the error is

egofetsting.png

Pull Request (PR):

When committing your final changes to GitHub and preparing to merge them into the teacher’s repository, you need to create a pull request. Before doing so, check the Actions tab to ensure there are no failed actions and all processes have completed successfully.To create a pull request, click the Contribute button at the top of your repository page. If you don’t see it, confirm that you forked the repository instead of using it as a template. Once the pull request is created, include a clear description of what you added or changed before submitting it.If the pull request is rejected, review the comments to understand the issues, make the necessary fixes, and resubmit promptly. This ensures your contributions are accurate and meet the requirements for approval.

eg

eg.png

merging:

Merging combines changes from one branch into another and is the core of pull requests. If you’re reviewing a pull request, check for conflicts (GitHub will highlight these) and review all changes for errors. If everything looks good, click the merge button.After submitting a pull request, don’t forget to sync your fork to avoid falling behind and causing new conflicts.

deployment:

Deployment occurs after any changes are made to your GitHub repository. You can monitor the process in the Actions tab of your repository. If the deployment fails, GitHub will provide an error message with details about the issue. In such cases, open VS Code, ensure you’ve pulled the latest changes, and run the make command. If make fails, it will indicate where the error is. If no issues are apparent, you can seek help using ChatGPT or another AI tool to troubleshoot. Once the deployment is successful, a link to your repository’s site will appear, allowing you to access it on any computer!