Git and GitHub Workflow | 1st Issue Ticket Task | Working with GitHub web UI

[Ifycode]

Background

Hi there, welcome to @collabocate-osc! We have created this first (1st) issue ticket task assignment for anyone who:

• Is new to Git and GitHub and wants to learn how to work with them, especially while collaborating with others.
• Is looking for a platform to learn Git and GitHub, while dealing with repository/project that is owned/maintained by someone else.
• Would like simple community tasks to understand @collabocate-osc's Git and GitHub workflow, before starting to contribute to community projects.

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

In this 1st task assignment, you are required to create a file with GitHub markdown content from the GitHub web User Interface. Find more information in the expected solution section below.

Expected solution

Tip

You are to create your branch, folder and file using the GitHub web User Interface.

• 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.
• Create a new folder called @replace-this-text-with-your-own-GitHub-username in the root of the repository that you are to do this task in and submit to (which repository is this? - see the additional context section below).
• Create a file called gitcollab-ui-task.md in the root of your newly created folder.
• Use the content of the ui-task.md file found at the root of this @gitcollab-learn folder, in your own newly created file. Once you read the content of the ui-task.md file, you will know what text to change or replace.
• Before you commit your changes i.e. before you click on the "commit changes" button, take a screenshot. You will need it for your pull request, to show proof that you used the GitHub Web Interface. Take note: Before making the screenshot, expand your browser to full screen mode. Make sure to scroll to the top of the page so that the top of the page is not cropped out. Here's an example screenshot from a contributor: https://github.com/user-attachments/assets/70d8cd84-be9a-4651-932f-71505438aff9

Additional context

• Let us know in the comment of this issue ticket (GitHub discussion) that you will be participating in this 1st task assignment. Ensure to tag @collabocate-osc/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/collabocate-osc/good-first-issue-GIT-solutions
• If you have any questions or need any clarification when working on this ticket, please use the #git-workflow-support channel in our discord community server.
• To help you better understand how to work with other contributors within @collabocate-osc 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): Copy and paste the testing checklist below (without this note) to your pull request body description 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.

• 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).
• The folder with its name having a mix of @ and my GitHub user name has been created in the root of the good-first-issue-GIT-solutions repository.
• A file called gitcollab-ui-task.md is in the root of my newly created folder.
• The gitcollab-ui-task.md file uses the content of the ui-task.md file found at the root of the @gitcollab-learn folder. I have also followed the directions in there to replace text where necessary.
• I have taken a screenshot to show that I used the GitHub Web Interface for this task, as specified in the issue ticket. I have added the screenshot to the screenshot section of my pull request's body description.
• I certify that I ran my checklist.

[Goodnews-code]

Hi @collabo-community/maintainers

I will be participating in this 1st task assignment.

[Ifycode]

👍🏼 @Goodnews-code

You don't need to format your comment as an header with markdown though. Maintainers don't get notified if done that way.

[BA-atomic]

Hi @collabo-community/maintainers
I'll be participating in this 1st task assignment

[Ifycode]

Welcome @BA-atomic
Please go ahead

Reply is late because community is on break till 15 January.

[OpeyemiAdeniji]

Hi @collabo-community/maintainers
I'll be participating in this first task assignment

[Ifycode]

Welcome 👍🏼

[KBandipo]

Hi @collabo-community/maintainers
I will be participating in this 1st task assignment.

[Ifycode]

🎉 @KBandipo

[Danbaba1]

Hi @collabo-community/maintainers
I will be participating in this 1st task assignment

[Ifycode]

🎉 @Danbaba1

[Oyebliss]

Hi @collabo-community/maintainers
I will be participating in this 1st task assignment.

[Ifycode]

🎉 @Oyebliss

[KamiNation]

Hi, @collabo-community/maintainers. I will be participating in this first task assignment.

[Ifycode]

👍🏼

[elizabethobiagba]

I will be participating in this 1st task assignment @collabo-community/maintainers

[Ifycode]

👍🏼

[oluwadamilola21]

Hi @collabo-community/maintainers
I'll be participating in this 1st task assignment

[Ifycode]

👍🏼

[Ifycode]

Important

The name of our community has changed from collabo-community to collabocate-osc. Please tag maintainers with @collabocate-osc/maintainers from now on. Thank you.

[Yanmi01]

Hi @collabocate-osc/maintainers,
I will be participating in this first task

[Ifycode]

👍🏼