Git and GitHub Workflow | 2nd Issue Ticket Task | Working with GitHub web UI #3
Replies: 6 comments 6 replies
-
Hi @collabo-community/maintainers, i will be participating in this 2nd task assignment. |
Beta Was this translation helpful? Give feedback.
-
Hi @collabo-community/maintainers I will be participating in this second issue ticket task |
Beta Was this translation helpful? Give feedback.
-
Hi @collabo-community/maintainers, i will be participating in this 2nd task assignment. |
Beta Was this translation helpful? Give feedback.
-
Hi @collabo-community/maintainers, i will be participating in this 2nd task assignment. |
Beta Was this translation helpful? Give feedback.
-
Hi @collabo-community/maintainers, |
Beta Was this translation helpful? Give feedback.
-
Hi @collabo-community/maintainers |
Beta Was this translation helpful? Give feedback.
-
Prerequisite
This 2nd task issue ticket is based on the 1st issue ticket in this Git and GitHub workflow series. To proceed with this 2nd task, ensure that you have submitted a pull request for the 1st task, and your 1st task's pull request has been approved.
If you have not done the 1st task, you can find it through the project board here: git and github workflow good first issue tickets
If your 1st task's pull request has been submitted and approved by a maintainer, you can proceed to do this 2nd 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
In this 2nd task assignment, you are required to make some changes to the markdown tutorial file that you created in the 1st task from the GitHub web User Interface. It will also involve learning how to merge conflicts. 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.
develop
branch with the @collabo-community repo'sdevelop
branch, so that your 1st task changes that we merged into our develop branch can reflect in your fork's develop branch.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.gitcollab-ui-task.md
file that you previously created (in the 1st task), change this line:To this instead:
Additional context
#good-first-issue-support
channel in our discord community server.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.
Replace this inline code block with the link to your approved 1st task pull request
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).gitcollab-ui-task.md
file in my own folder, as directed in the 2nd issue ticket task.Beta Was this translation helpful? Give feedback.
All reactions