Git and GitHub Workflow | 3rd Issue Ticket Task | Working with GitHub web UI

[Ifycode]

Prerequisite

This 3rd task issue ticket is based on the 1st - 2nd issue tickets in this Git and GitHub workflow series. To proceed with this 3rd task, ensure that you have submitted pull requests for all the previous tasks, and your pull requests for all the previous tasks have been approved.

If you have not done any or all of the previous tasks, you can find them through the project board here: git and github workflow good first issue tickets

If your pull requests for all the previous tasks have been submitted and approved by a maintainer, you can proceed to do this 3rd task.

Helpful resource

This youTube playlist will give you an idea of how to work with GitHub web User Interface: https://youtube.com/playlist?list=PLMDhbo3xlD1ESa1_9WN4yG7bGDDksEQx7&si=F9lzacG1cr9WGS-M

Issue description

Well done, and nice work so far!
In this 3rd task assignment, you are required to rename the markdown tutorial file that you created in the one of the previous tasks from the GitHub web User Interface. Find more information in the expected solution section below.

Expected solution

Tip

You are to sync your fork, create your branch, and make the changes to the already existing files or folders using the GitHub web User Interface.

• You may have to first sync your fork's develop branch with the @collabo-community repo's develop branch, so that your previous tasks' changes that we merged into our develop branch can reflect in your fork's develop branch.
• Create a new branch from the develop branch. Your branch name should be @GH-replaceThisPartAfterTheHyphenWithTheIssueNumberForThisTicket (don't add the # sign to the ticket number, and no space in there). It is in this new branch that you should make your changes in and submit from.
• Rename thegitcollab-ui-task.md file that you previously created to gitcollab-web-ui-task.md

Additional context

• Let us know in the comment of this issue ticket (GitHub discussion) that you will be participating in this 3rd task assignment. Ensure to tag @collabo-community/maintainers in your comment. That way, maintainers will be notified and will be prepared to help review your pull request when you submit.
• Repo URL (where you are to do and submit this task to): https://github.com/collabo-community/good-first-issue-solutions
• If you have any questions or need any clarification when working on this ticket, please use the #good-first-issue-support channel in our discord community server.
• To help you better understand how to work with other contributors within the @collabo-community better, we will review your pull request based on the directions given in this issue ticket and our Public Documentation Resource Guide.

Testing checklist

Note (to contributor taking on this task assignment): Add the testing checklist below (without this note) to your pull request when submitting your fix. This will guide (you and) the contributors who will review your fix to know what is important to check or test for.

• Here's a link to my approved 2nd task pull request: Replace this inline code block with the link to your approved 2nd task pull request
• My branch for this task assignment is created from the develop branch, and the name of my branch is a mix of @GH- and the ticket's issue number (no # sign and no space in there).
• I have renamed thegitcollab-ui-task.md file in my own folder to gitcollab-web-ui-task.md
• I certify that I ran my checklist.

[Goodnews-code]

Hi @collabo-community/maintainers, i will be participating in this 3rd assignment task.

[Ifycode]

👍🏼

[BA-atomic]

Hi @collabo-community/maintainers, i will be participating in this 3rd assignment task.

[Ifycode]

👍🏼